3.3Resource planning and team development

A project team does not perform at a high level from the moment it forms—it matures into a functioning team only by passing through stages. What matters for a PM is not memorizing the names of the Tuckman model's stages but discerning which stage the team is currently in and how to engage with the friction characteristic of that stage. This section covers clarifying roles (RAM/RACI), the team maturation process, choosing among motivation theories, and resource leveling, together with real team-management judgments.

3.3.1Clarifying roles with RAM/RACI

• A RAM (responsibility assignment matrix) cross-references WBS work packages (rows) against project members (columns) to lay out who is responsible for what. It is used to surface overlaps or gaps in role assignment.
• RACI is a representative RAM format that specifies each task's involvement in four categories: Responsible (does the work), Accountable (owns the final decision/sign-off), Consulted (a two-way input source), and Informed (a one-way notification recipient). The key point is that there should be exactly one Accountable person per task as a rule, so decision ownership is unambiguous.
• A practical pitfall: if a task has multiple Accountable people (or none), no one owns the final call when a problem arises, and decision-making stalls. When reviewing a RACI chart, the PM should check the Accountable column for duplicates or blanks first.

3.3.2Team development via the Tuckman model

• Forming: members barely know each other, and understanding of roles or objectives is still shallow. Surface-level politeness dominates while candid exchange is rare. The PM should take the lead in orienting the team by clearly presenting the purpose, roles, and ways of working.
• Storming: conflicting opinions, role struggles, and friction over ways of working surface. Productivity often dips temporarily, but this is not an abnormal event—it is a necessary passage on the way to team maturity. Rather than forcibly suppressing conflict, the PM should facilitate, framing it as constructive discussion and driving toward consensus.
• Norming: having worked through conflict, the team settles into shared working rules, role divisions, and communication norms. Mutual trust starts to form and a cooperative atmosphere emerges. The PM should gradually reduce fine-grained intervention and draw out the team's autonomy.
• Performing: the team achieves results with high autonomy and mutual complementarity—the most productive stage. The PM delegates day-to-day operation to the team and focuses on a supporting role: removing obstacles and coordinating externally.
• Adjourning: the team disbands as the project closes out. The PM leads handover of results, recording lessons learned, and evaluating and recognizing members.
• A key practical point: misreading storming-stage conflict as "the team has become dysfunctional" and hastily replacing members is a classic mistake—conflict is often a normal process on the way to norming, and facilitation should be tried first.

3.3.3Choosing between motivation theories, and resource leveling

• Maslow's hierarchy of needs explains human motivation as a hierarchy from physiological needs up to self-actualization. It suits diagnosing a situation of "are the member's more basic needs (job security, a safe working environment, etc.) not being met?"
• Herzberg's two-factor theory distinguishes motivator factors that create satisfaction (achievement, recognition, the intrinsic interest of the work, growth opportunities) from hygiene factors that only prevent dissatisfaction (pay, working conditions, interpersonal relations, company policy). It suits the judgment that "however much hygiene factors are improved, satisfaction does not rise—only dissatisfaction is prevented—so raising motivation requires addressing motivator factors."
• The practical distinction: Maslow suits diagnosing a lack of basic needs (the root cause of anxiety or dissatisfaction), while Herzberg suits diagnosing a mix-up between hygiene and motivator factors, such as "we raised pay, but motivation did not improve."
• Resource leveling smooths out fluctuations in resource (staffing) demand by shifting activity start/finish times within the available float of non-critical activities, avoiding a pileup of resource demand in a specific period. It is important to understand that leveling sometimes consumes float without extending the project completion date, and sometimes float is insufficient, pushing the completion date out.

Suppose a PM is leading a newly formed project team. In week 1, most members are meeting each other for the first time, and meetings are full of surface-level agreement with no substantive debate. Here, in keeping with forming, the PM should take the lead in orienting the team: clearly presenting the project's purpose, each member's role (made explicit in a RACI chart), and the ground rules for how the team will work. By week 3, the situation flips: fierce disagreement erupts over the design approach, meetings become contentious, and team productivity temporarily dips. If the PM, seeing this, concludes "the team has become dysfunctional" and rushes to remove the most contentious member from the project, that is a classic mistake. This is a characteristic phenomenon of storming—in fact a normal passage toward maturity, in which the team is voicing honest opinions and starting to seriously grapple with work rules and role division. What the PM should do is not forcibly suppress the conflict but facilitate: organize the points of contention and steer toward constructive consensus. Additionally, suppose a member confides, "even though my pay was raised from last year, I actually feel less motivated than before." This can be explained by Herzberg's two-factor theory: pay is a hygiene factor (it only prevents dissatisfaction) and does not by itself create satisfaction or motivation, so the diagnosis is that the PM needs to address motivator factors—achievement, autonomy, growth opportunities. On the other hand, if another member confides, "I'm anxious because it's unclear whether my contract will be renewed," that is a situation where Maslow's safety needs are not being met, and resolving that basic anxiety should be the priority first. Discerning that the same surface symptom ("a motivation problem") calls for a different theory and response depending on the root cause—a lack of basic needs versus a mix-up between hygiene and motivator factors—is the PM's role.

3.3.4Section summary

• RACI clarifies decision ownership by assigning exactly one Accountable person per task
• The Tuckman model progresses forming -> storming -> norming -> performing -> adjourning; the storming-stage productivity dip is a normal passage, and the PM should shift to facilitation
• Choose a motivation theory by root cause: a lack of basic needs -> Maslow; a hygiene/motivator mix-up -> Herzberg