A perfect schedule and budget mean nothing if the team assigned to execute them is unmotivated, in conflict, or simply not yet functioning as a team. PM4040 treats human resource management as a discipline with its own models and stages, not an afterthought to the technical planning done in earlier PM courses.
Tuckman's stages of team development
PM4040 uses Bruce Tuckman's model — forming, storming, norming, performing, and adjourning — to teach that every team predictably moves through friction before it becomes productive. In forming, members are polite and uncertain of roles; in storming, conflict emerges as personalities and working styles clash; in norming, the team establishes working agreements and trust; in performing, the team operates with minimal supervision at high output; and in adjourning, the team disbands at project close. Students learn that a project manager's leadership style should shift across these stages — more directive during forming and storming, more delegative during performing.
Motivation theory applied to project teams
The course applies classic motivation theories — Maslow's hierarchy of needs, Herzberg's two-factor theory (hygiene factors vs. true motivators), and McGregor's Theory X/Theory Y — to the specific challenge of motivating project team members who are frequently borrowed from functional departments and have competing priorities. Herzberg's distinction is emphasized: fixing hygiene factors (pay, working conditions) only prevents dissatisfaction, while true motivation comes from achievement, recognition, and meaningful work — which a project manager without formal authority over pay or promotions must still find ways to provide.
Key topics in PM4040
- Tuckman's five stages: forming, storming, norming, performing, adjourning
- Situational leadership: matching leadership style (directive vs. delegative) to team maturity
- Maslow's hierarchy of needs and Herzberg's two-factor theory applied to project work
- Power types available to a PM: formal, reward, expert, referent, and coercive power
- Conflict resolution modes: collaborating, compromising, forcing, avoiding, and smoothing
- Resource allocation and leveling: resolving over-allocation without extending the schedule unnecessarily
- Virtual and matrix-team challenges: motivating team members who report to a different functional manager
Working on a team-development analysis or a motivation-theory case study?
Our project management experts build PM4040-level coursework grounded in real HR and motivation frameworks.
Worked example: applying Tuckman to a struggling project team
- Situation: Three weeks into a cross-functional project, team members are disagreeing openly about how to divide the work — classic storming
- Wrong response: PM avoids the conflict, hoping it resolves itself
- Correct response: PM facilitates a working-agreement session, clarifies roles and decision rights, and uses a collaborating conflict style to surface the underlying disagreement
- Outcome: Team moves into norming within two weeks, with clearer roles and a documented decision-making process the whole team helped write
Get Help With PM4040
Team-development analyses, motivation-theory papers, conflict-resolution case studies.
Place Your OrderView All ServicesRelated courses
Frequently asked questions
Bruce Tuckman's model describes the predictable sequence most teams move through: Forming (members are polite, uncertain, and dependent on the leader for direction), Storming (conflict emerges as roles, working styles, and priorities clash — the most difficult but necessary stage), Norming (the team establishes shared working agreements, trust builds, and roles clarify), Performing (the team operates with high output and minimal supervision, resolving issues independently), and Adjourning (the team disbands at project completion, often with a sense of loss for high-performing teams). PM4040 teaches that storming is not a sign of team failure — it is a necessary and expected stage, and a project manager who suppresses conflict during storming rather than facilitating it through often delays the team's arrival at performing.
Frederick Herzberg's two-factor theory distinguishes between hygiene factors — things like pay, job security, working conditions, and company policy — and true motivators, like achievement, recognition, responsibility, and meaningful work. The key insight is that these are not opposite ends of the same scale: improving hygiene factors can only reduce dissatisfaction, it cannot create satisfaction or motivation, while improving motivators can genuinely increase engagement and effort. For a project manager, this matters because most PMs have no control over a team member's salary or job title (hygiene factors are usually controlled by the functional manager) — but a PM has significant control over motivators: assigning meaningful, visible work, publicly recognizing contributions, and giving team members real ownership over decisions. PM4040 uses this distinction to teach that PMs should focus their limited influence on motivators, not assume that hygiene improvements alone will drive performance.