Video summary

ManPro09 Manajemen Sumberdaya Proyek

Main summary

Key takeaways

Educational

Main Ideas & Lessons (Project Resource Management + Human Behavior)

The speaker introduces Project Resource Management in project management from both a theoretical and practical perspective. A core message is that resources are not only tools or materials—people (human resources) are the most important resource, and their motivation and behavior strongly influence project success.

Key themes

  • Resource management is essential because demand for human resources (HR) can fluctuate and increased significantly during/after the pandemic.
  • Project success depends on managing:
    • Human resources: motivation, personality, leadership style, conflict behavior, emotional intelligence
    • Non-human resources: facilities, equipment, materials, consumables
  • Effective management applies:
    • management processes
    • theories of motivation, influence, and leadership
    • team practices

Methodology / Instruction-Like Content

A) Definition of Project Resources (What Is Managed)

Project resources include:

  • Human Resources (HR)
  • Facilities
  • Equipment
  • Raw materials
  • Consumables
  • Other supporting resources

B) Six Main Process Steps in Project Resource Management

  1. Planning resource management
  2. Estimating activity resources (estimating what resources activities require)

  3. Developing the project team Build and improve the team so it can carry out the work.

  4. Managing the project team Coordinate, support, motivate, and lead performance.

  5. Controlling resources Monitor and adjust resource usage to keep it aligned with the plan.

  6. The speaker frames these steps as a continuous flow: planning → estimating → team development → team management → control

C) Concepts / Underlying Theories for Managing People (Why People Are Hard to Manage)

People are harder to manage than “things” because they have different:

  • desires, hopes
  • motivations, needs

The speaker then connects multiple theories to project management.

1) Maslow’s Hierarchy of Needs (Motivation Ladder)

People are motivated by fulfilling needs in levels:

  • Physical needs (food, drink)
  • Safety needs (security, shelter, protection)
  • Social needs (friendship, love/belonging)
  • Esteem needs (respect, status, recognition)
  • Self-actualization (challenge, innovation, creativity)

Key principle: If lower needs are met, they stop motivating; people move toward higher-level needs.

2) Herzberg’s Motivation–Hygiene Theory

Two categories:

  • Motivators (increase satisfaction/motivation)
    • achievement, recognition, responsibility, progress
    • the work itself, relationships
  • Hygiene factors (prevent dissatisfaction)
    • salary/benefits, working conditions
    • supervision, policies, environment

Key principle:

  • Missing hygiene factors causes dissatisfaction
  • Having hygiene factors alone may not strongly motivate

3) McClelland’s Theory of Needs

Three acquired/learned needs:

  • Achievement: values challenging goals/projects
  • Affiliation: wants acceptance and harmonious relationships
  • Power: seeks personal or institutional power

Project manager implication: Identify the person’s dominant need using:

  • conversations/interviews
  • observation of behavior Then align motivation accordingly.

4) McGregor’s Theory X and Theory Y (Assumptions About Workers)

  • Theory X: people dislike work, avoid responsibilities → management uses coercion/threat/control
  • Theory Y: work can be natural → people seek responsibility → management enables freedom and development

Also briefly mentions Theory Z (Japanese approach):

  • trust, quality, collective decision-making

5) Power Theory (Influence Types)

Power is the ability to influence behavior. Five types mentioned:

  • Coercive (corrosive): punish/threaten
  • Legitimate: based on formal position
  • Expert: based on expertise (e.g., doctors, advisors)
  • Reward: bonuses/benefits
  • Referent (reference/reputation): people obey because they admire/want recognition

Key principle: Use the right power for the right situation.

D) Influence in Project Management (Thamhain & Wilemon-Style Factors)

The speaker notes that projects succeed when managers can influence without relying only on authority/money/penalties. Nine influence factors are listed:

  1. Authority — decisions via hierarchy
  2. Assignment — allocate tasks and direct future work
  3. Budget — control/discretion over project resources
  4. Promotion — career advancement
  5. Money — control over salary/benefits
  6. Penalty — impose consequences/punishment
  7. Work — make work meaningful/pleasant so people want to do it
  8. Skill (expert knowledge) — people comply due to expertise/certifications
  9. Friendship — build friendly relationships to gain cooperation

E) “7 Habits of Highly Effective People” (Covey) Applied to Project Management

Recommended habits, tailored to project behavior:

  1. Be proactive
  2. Begin with the end in mind
  3. Put first things first
    • prioritize
    • use checklists to “organize time”
    • avoid wasting time on minor non-urgent tasks
  4. Think win–win
  5. Seek first to understand, then to be understood
  6. Synergize (aim for “1 + 1 = 3”)
  7. Sharpen the saw (continuous improvement—don’t rely on being “fed” information)

F) Emotional Intelligence (Definition + Relevance)

Emotional intelligence includes:

  • understanding your own emotions
  • understanding other people’s emotions

The speaker links emotional stability to better project performance:

  • managing self
  • relating to others
  • achieving targets

Practice recommendation: Repeated team/project involvement helps build emotional intelligence over time.

G) Leadership Style (Situational Leadership)

Leadership effectiveness is presented as situational, referencing a model attributed to Bowman, plus “visual/leadership styles” described as:

  • Visionary — guide with a vision
  • Coaching — develop people
  • Democratic / affiliative — invite participation
  • Authoritative / commanding — direct instruction
  • Laissez / “visiting” — urging quick completion (briefly described)

Lesson: Choose leadership style based on the situation and team needs, and learn through experience.

H) Project Manager Competencies (PMI Standards Mentioned)

The speaker states that, per PMI, project managers need:

  1. Technical/proficiency capability Understand domain and lifecycle well enough to lead.

  2. Strategic & business management Understand finance/cost control basics and business impact.

  3. Leadership Guide, motivate, and adapt to team and situation.

I) Project Resource Management Process Details (Practical Breakdown)

1) Planning (What to Do in Planning Resources)

  • Identify physical resources:
    • how many people
    • required machines/facilities
    • organize responsibilities and reporting relationships
  • Create an organizational structure (especially for large projects)
    • hierarchy (PM, deputies, leads, professionals, etc.)

  • Define roles/jobs Example: clarify purchasing responsibilities (contracts, procurement tasks).

  • Define scope and task breakdown Translate project scope into activities.

  • Use responsibility tools (conceptually a RACI-like responsibility matrix) Clarify who is Responsible / Accountable / Consulted / Informed.

Importance emphasized: If responsibilities are unclear, the organization becomes confused and project achievement becomes harder.

2) Estimating Resources

  • Estimate “how many” resources are needed to meet timelines/goals Example logic: finishing a 300 m² house in 3 months requires realistic staffing—too few people makes the deadline impossible.

  • Consider project structure:

    • multiple modules in software vs. a single program changes resource/cost estimates
  • Produce estimation outputs:
    • often visualized via charts/histograms by time (months) and roles

3) Resource Allocation & Loading

  • Allocate physical resources to tasks/activities.
  • Use workload loading to:
    • reduce management burden
    • reduce costs
    • avoid under/overstaffing and protect morale

4) Resource Leveling

When workloads are uneven (some overloaded, others idle), apply resource leveling:

  • redistribute work across time to reduce overtime and overload
  • reduce idle periods (avoid unemployment)

Note: Parallel work can sometimes increase overall completion time, so leveling can help.

5) Developing the Project Team

  • Improve skills via training.

  • Use team-building tools:

    • MBTI to understand personality preferences (e.g., extrovert/introvert, sensing/intuition, thinking/feeling, judging/perceiving)

  • Also mentions social style profiles and team behavior styles, such as:

    • expressive, analytical, amiable, driver with traits like creativity, critical thinking, conflict style, preference for routines vs variety.

6) Managing Conflicts and Agreements

Conflict-handling tools mentioned include:

  • reward/recognition systems
  • conflict resolution styles:

  1. Confrontation (problem solving) High concern for both task and relationship

  2. Compromise Middle ground

  3. Smoothing / Accommodating Focus on relationships; reduce task friction

  4. Withdrawal Step back when stakes are low or conflict is too high

  5. Collaborating Integrate perspectives for consensus (high relationship + high task)

Warnings / insights:

  • Conflict can be useful if it is task-related (new ideas, better motivation).
  • Emotional conflict often reduces performance.

7) Team “Dysfunctions” (Book Referenced)

A book is referenced (described as very deep). It lists five team dysfunctions:

  1. Absence of trust
  2. Fear of conflict
  3. Lack of commitment
  4. Avoiding accountability
  5. Inattention to results

Lesson: These issues can destroy a project; addressing them helps teams succeed.

8) Controlling Resources (Final Process Step)

  • Implement controls so execution matches the plan.
  • Monitor goals and alignment.
  • Apply preventive/corrective actions (described as “alarms” and corrections).
  • Without control:
    • the organization can lose control
    • people may spend resources improperly
    • the organization may become chaotic and lose money/resources

Speakers / Sources Featured (As Mentioned)

Speakers / Authors / Referenced Persons

  • Main lecturer/speaker (unnamed; provides the content throughout)
  • Abraham Maslow — Hierarchy of Needs
  • Frederick Herzberg — Motivation–Hygiene theory
  • David McClelland — Achievement/Affiliation/Power needs
  • Douglas McGregor — Theory X and Theory Y (plus mention of Theory Z)
  • Thamhain & Wilemon — influence theory with nine factors (spelled in the notes as “Thamhain and Philemon”)
  • Gardner (Howard Gardner) — mentioned in connection with emotional intelligence/multiple intelligences
  • Bowman — leadership model reference
  • Peter Drucker? — mentioned as not explicitly included / no clear citation

Institutions / Standards

  • PMI (Project Management Institute) — project manager competency components and standards

Books Referenced

  • “Seven Habits of Highly Effective People” (Covey)
  • A team leadership/management book referencing “five dysfunctions of a team” (title not clearly provided in the subtitles)

Tools / Framework Names

  • MBTI
  • DISC (referred to in subtitles, phrased as “disc2/dcdc”)
  • RACI / responsibility matrix idea (concept present; RACI not explicitly spelled out)

Original video