Forming Storming Norming Performing Adjourning is a five-stage model of team development that describes the predictable behavioral and relationship phases a project team passes through from initial assembly to eventual disbanding. The model emerged from group dynamics research and has become a common reference in project management for interpreting team friction, productivity shifts, and leadership needs. Project managers apply the framework to anticipate conflict, adjust their management style, and explain team behavior to sponsors and stakeholders. Although the stages are often drawn as a straight line, real project teams move through them in cycles, sometimes repeating stages when membership, scope, or pressure changes.
Summary Table: Forming, Storming, Norming, Performing, Adjourning
| Key Concept | Summary |
|---|---|
| Team Development | Tuckman's five-stage model identifies the recurring behavioral and interpersonal phases project teams navigate, from initial assembly through active collaboration to final disbanding. |
| Origins | Rooted in group dynamics research, the model has become a standard project management lens for diagnosing team friction, shifts in productivity, and evolving leadership demands. |
| Non-Linearity | While the stages are commonly depicted as linear, project teams typically cycle through them and may revisit earlier stages when membership, scope, or pressure change. |
| Tuckman Model | Bruce Tuckman introduced the sequential model of group development in 1965. The adjourning phase was added later to reflect team closure. |
| Descriptive Nature | The model is descriptive rather than prescriptive. It identifies common patterns without assuming every team experiences each stage with equal intensity or duration. |
| Forming | During forming, project managers can reduce ambiguity by clarifying objectives, facilitating introductions, and establishing basic ground rules while team members remain polite and guarded. |
| Storming | Conflict during storming may appear disruptive, but it often signals that the team is beginning to engage authentically with the work, its constraints, and each other. |
| Adjourning | During adjourning, managers can support the team by recognizing contributions, documenting lessons learned, and providing a clear sense of closure as the project ends. |
What Is Forming Storming Norming Performing Adjourning?
The Forming Storming Norming Performing Adjourning definition refers to a sequential model of group development introduced by Bruce Tuckman in 1965 and later expanded to include the adjourning phase. Tuckman's original framework described four stages: forming, storming, norming, and performing. In 1977, Tuckman and Mary Ann Jensen added adjourning to account for the termination of temporary groups. The model is descriptive rather than prescriptive, meaning it identifies common patterns without claiming that every team must experience each stage with equal intensity or duration. Within project management, the model is used as a diagnostic lens rather than a rigid maturity scale.
Origin and History of Forming Storming Norming Performing Adjourning
Tuckman developed the model after reviewing a broad body of small-group research from therapy, education, and organizational settings. His 1965 article, "Developmental sequence in small groups," proposed that groups generally move through distinct interpersonal and task stages as they mature. The later addition of adjourning reflected the reality that many groups, including project teams, have a defined end point. The model's background outside project management helps explain why it is widely accepted across disciplines, but its temporary-team logic makes it especially useful for projects. In project work, team members rarely have years to settle into stable roles, so the stages often unfold quickly and under pressure.
Core Meaning of Forming Storming Norming Performing Adjourning
The core meaning of Forming Storming Norming Performing Adjourning is not that teams improve automatically. Rather, the model says that tension, role negotiation, and relationship building are normal parts of team development. A team that moves from polite formality into open disagreement is not necessarily failing. It may be entering storming, which is often a sign that members are invested enough to raise concerns. The framework helps project managers distinguish productive friction from destructive conflict. For a new project manager, this distinction can feel counterintuitive: conflict can look like a problem when it is actually evidence that a team is beginning to engage with the work.
Key Insights on Tuckman's Group Development Model
- Rooted in Small-Group Research
- Bruce Tuckman introduced the model in 1965 after synthesizing research on small groups across therapeutic, educational, and organizational contexts, then published the framework in his article "Developmental sequence in small groups."
- Adjourning Added in 1977
- Tuckman and Mary Ann Jensen added the adjourning stage in 1977 to capture how temporary groups disengage and conclude their work, recognizing that project-based teams commonly reach a defined endpoint.
- Descriptive Rather Than Prescriptive
- The model describes recurring patterns in group development rather than prescribing a rigid sequence, allowing for variation in the intensity, duration, and even occurrence of each stage across different teams.
- Especially Useful for Project Teams
- Because the model accounts for time-limited group life cycles, it is especially relevant to project teams that must form, perform, and dissolve quickly, often under significant deadline and resource pressure.
Key Components of Forming Storming Norming Performing Adjourning
The key components of Forming Storming Norming Performing Adjourning are the five stages themselves, each defined by characteristic behaviors, leadership demands, and task outputs. These stages are not isolated events; they overlap and can repeat. Understanding the components helps project managers choose appropriate interventions, from clarifying roles in forming to celebrating closure in adjourning. The model also implies that team productivity is rarely constant across a project.
Forming Stage
The forming stage is marked by orientation, politeness, and dependence on formal leadership. Team members may be enthusiastic but uncertain about their roles, the project's boundaries, and how decisions will be made. They often avoid serious disagreement because relationships are new. Productivity in forming is typically low, not because people lack skill but because they are still learning how to work together. Project managers can support forming by providing clear objectives, introducing team members, and establishing basic ground rules. A project charter or team charter review at kickoff is a common forming-stage activity.
In practice, forming feels similar to the first week of a new assignment: people are courteous, questions are guarded, and most eyes turn to the project manager before any significant decision. That deference is normal, but it can create a false sense of smooth progress. Experienced project managers watch for unspoken concerns during forming because those concerns often become the first storming triggers.
Storming Stage
Storming is the stage where differences emerge. Team members may disagree about priorities, technical approaches, resource allocation, or their own roles. Subgroups can form, and resistance to the project manager's authority may surface. Some teams experience loud, visible conflict; others experience quiet disengagement or passive resistance. Storming can feel chaotic, but it often represents a necessary negotiation of influence and expectations. The project manager's role shifts from directing to facilitating, mediating disputes, and keeping disagreements focused on tasks rather than personalities. Avoidance of all conflict during this stage can delay the norming stage or force unresolved issues underground.
A practical example is a software team debating two architectural patterns. The disagreement may appear to be a sign of dysfunction, but if the arguments are about trade-offs, maintainability, and delivery risk, the team is actually working through technical uncertainty. Suppressing that debate to maintain surface harmony would likely push the unresolved decision into later stages where it becomes more expensive.
Norming Stage
In norming, the team develops shared expectations and working agreements. Roles become clearer, trust increases, and members begin to use "we" language. Feedback becomes more direct, and procedures for resolving issues are better accepted. The project manager can step back from day-to-day mediation and support the team's emerging norms. Norming does not mean the absence of disagreement; it means disagreement is handled through agreed-upon channels. The risk in norming is groupthink, where the desire for cohesion suppresses necessary dissent.
Norming often happens gradually and almost invisibly. A project manager may notice that meetings shift from tense debates to shorter problem-solving discussions. Team members start volunteering for tasks instead of waiting to be told. These small behavioral changes are signs that the team has begun to regulate itself.
Performing Stage
Performing is characterized by high autonomy, interdependence, efficient communication, and constructive use of differences. The team can solve problems without constant oversight, and members hold each other accountable. The project manager's role becomes more about removing external obstacles and providing strategic context than about directing daily work. Not every team reaches performing, and reaching it once does not guarantee staying there. A change in membership, a major scope shift, or a deadline crisis can push a performing team back into storming.
Performing teams are often described as greater than the sum of their parts, but that phrase should not suggest effortless work. High performance still requires effort, conflict, and renegotiation. The difference is that the team has developed enough trust and process maturity to handle those challenges without falling apart.
Adjourning Stage
Adjourning is the final stage, when the project ends and the team disbands. Members may feel pride, relief, sadness, or anxiety about their next assignment. Some practitioners refer to this phase as mourning because the loss of identity and relationships can be real. Project managers should recognize that closure matters for morale and knowledge transfer. A formal closeout that acknowledges contributions, documents lessons learned, and clarifies transition responsibilities can reduce the sense of abrupt loss. Teams that skip deliberate adjourning may leave members with unresolved frustrations and weaker institutional memory.
In projectized organizations, adjourning can happen quickly. One week the team is fully engaged; the next week members are reassigned to other projects. A short retrospective or a simple acknowledgment of what the team accomplished can provide the psychological closure that supports future collaboration. The absence of closure rarely shows up in a project's technical metrics, but it affects how people carry lessons and attitudes into the next team.
Forming Storming Norming Performing Adjourning in PMBOK and Predictive Project Management
The Forming Storming Norming Performing Adjourning PMBOK connection appears most directly in the Develop Team process within the Resource Management knowledge area. In predictive project management, the PMBOK Guide references team development models as tools for improving competencies, interactions, and the overall team environment. The model helps a project manager understand why a newly formed team may underperform despite individual competence. It also supports the creation of team performance assessments by giving a vocabulary for observed behaviors. The Develop Team process sits in the Executing process group, which is when many of the stage transitions become visible.
Use of Forming Storming Norming Performing Adjourning in Predictive Life Cycles
In a traditional predictive project, forming often aligns with project initiation and early planning, when roles and expectations are being set. Storming may appear during detailed planning or early execution, as technical disagreements and resource pressures intensify. Norming often emerges as the team settles into established delivery rhythms. Performing is most likely during steady-state execution, provided the team has navigated earlier stages successfully. Adjourning corresponds to project closing and the release of resources. The alignment is useful for planning team development activities, but it is not exact. Phase gates, new stakeholders, and baseline changes can pull a team back to forming or storming at any point.
Key Takeaways on PMBOK Team Development Stages
- Develop Team Process Connection
- The Tuckman model aligns most closely with the Develop Team process in the Resource Management knowledge area, and its stage transitions become most visible during the Executing process group.
- Explaining Early Team Underperformance
- The model explains why a newly formed team can underperform initially even when every individual member is highly competent, because members are still negotiating roles, relationships, and shared working norms.
- Supporting Team Performance Assessments
- It provides project managers with a shared vocabulary for observed behaviors, which supports more structured and objective team performance assessments instead of relying on informal impressions.
- Stage Alignment in Predictive Life Cycles
- In predictive projects, forming typically aligns with initiation and early planning, storming with detailed planning or early execution, norming with settled delivery rhythms, and performing with steady state execution. Phase gate reviews or baseline changes can nevertheless push a team back into earlier stages.
Forming Storming Norming Performing Adjourning in PRINCE2
The Forming Storming Norming Performing Adjourning in PRINCE2 relationship is implicit rather than prescriptive. PRINCE2 does not formally define Tuckman's stages, but its process model creates natural moments for team development. Starting up a Project and Initiating a Project resemble forming, because they establish roles, controls, and reporting lines. Early work package delivery can surface conflict that resembles storming, especially when the project board imposes constraints. As the team learns to manage stage boundaries and deliver products consistently, norming and performing behaviors become visible. Closing a Project is the formal adjourning phase, where the project management team confirms acceptance, reviews benefits, and disbands.
PRINCE2's separation of project manager and team manager roles means that the team manager often deals with forming and storming at the delivery level while the project manager focuses on stage control. The model remains a useful backdrop because PRINCE2's emphasis on management products does not remove the human need for trust, role clarity, and closure. A PRINCE2 project can have flawless stage plans and still struggle if the team has not moved past storming. For this reason, practitioners often use the model informally to diagnose delivery problems that process compliance alone cannot explain.
Forming Storming Norming Performing Adjourning in Agile and Hybrid Environments
The Forming Storming Norming Performing Adjourning in Agile context is nonlinear, compressed, and often repeated. Agile teams do not necessarily move through the stages once over a long project; they may cycle through them within a single sprint or release. Sprint planning clarifies roles and scope, which supports forming. Daily scrums can expose friction, which mirrors storming. Retrospectives and working agreements support norming. A mature Scrum team may hit performing during late sprints, but a membership change or a difficult product increment can reset the pattern. Adjourning occurs when the team dissolves, when the product reaches end of life, or when the team composition changes significantly.
Hybrid environments add another layer of complexity. A stable core team may remain in performing while temporary specialists join for specific phases, forcing small re-forming and storming loops. The model helps agile coaches and project managers avoid the mistake of assuming that a team that performed well last quarter will automatically perform well this quarter. It also suggests that time-boxed ceremonies are not a substitute for genuine team development. Retrospectives can support norming, but they cannot force trust if unresolved storming continues outside the meeting.
Key Insights on Agile Team Development Cycles
- Nonlinear, Compressed Stage Cycles
- Agile teams frequently revisit forming, storming, norming, performing, and adjourning within a single sprint or release, rather than progressing through these stages once over the course of a long project.
- Ceremonies Mirror Specific Stages
- Sprint planning reinforces the forming stage by clarifying roles and scope, while daily scrums often surface the interpersonal friction characteristic of storming.
- Performing Is Easily Reset
- Even a mature Scrum team that reaches the performing stage in later sprints can regress to earlier stages after a change in membership or a particularly demanding product increment.
- Adjourning Has Several Triggers
- The adjourning stage is triggered by team dissolution, product end of life, or a significant shift in team composition.
- Ceremonies Cannot Replace Development
- Time-boxed ceremonies and retrospectives can reinforce the norming stage, but they cannot manufacture trust or replace genuine team development when unresolved storming persists outside formal meetings.
BVOP Perspective on Team Development
The BVOP perspective on Forming Storming Norming Performing Adjourning reflects Business Value-Oriented Project Management's treatment of employee-created tools as formal products and its requirement for cross-functional teams. Cross-functional teams often surface storming earlier because different disciplines bring different assumptions, but they can reach performing faster when role clarity and value focus are explicit. BVOPM also treats scope change as user feedback rather than failure, which reduces the storming triggered by shifting requirements.
Purpose and Importance of Forming Storming Norming Performing Adjourning
The purpose and importance of Forming Storming Norming Performing Adjourning lies in its ability to turn confusing team friction into a recognizable and manageable pattern. Without the model, a project manager might interpret storming as personal failure or team dysfunction and intervene in ways that suppress necessary negotiation. With the model, the same behavior can be understood as a normal phase that requires facilitation, not punishment. The framework also helps sponsors and senior stakeholders understand that team productivity generally takes time to develop. It provides a rationale for investing in kickoff meetings, team charters, and ongoing team development activities.
Value of Forming Storming Norming Performing Adjourning for Project Managers
For project managers, the model is a planning and risk management tool. It suggests when to expect lower productivity, when to emphasize conflict resolution, and when to delegate more freely. It also informs communication planning: during forming, messages should be more directive; during performing, they can be more collaborative. The model supports stakeholder management by giving the project manager language to explain why a new team may not deliver at full speed immediately. It is not a precise predictor, but it is a useful heuristic for anticipating the human side of project delivery.
Key Insights on Team Development Stages
- Turns friction into a pattern
- The model converts ambiguous team friction into a predictable sequence, allowing leaders to anticipate conflict and respond with confidence instead of apprehension.
- Prevents misreading storming behavior
- Without this framework, project managers often mistake the storming phase for interpersonal failure or team dysfunction and may intervene in ways that unintentionally suppress the healthy negotiation required for group cohesion.
- Justifies investment in team building
- The framework provides sponsors and senior stakeholders with a clear business rationale for investing in kickoff meetings, team charters, and structured development activities that accelerate team maturity.
- Guides timing of managerial interventions
- For project managers, the model identifies periods of expected productivity decline, highlights when conflict resolution should take priority, and signals the point at which greater delegation becomes appropriate.
- Shapes communication and stakeholder messaging
- It clarifies the appropriate balance of directive and collaborative communication at each stage and provides leaders with language to explain why new teams often need time before reaching full delivery speed.
Common Challenges, Pitfalls, and Misconceptions
Several misconceptions about Forming Storming Norming Performing Adjourning persist in project environments. The most common is that teams move through the stages once, in order, and then remain in performing. In reality, teams regress when membership changes, scope shifts, or deadlines tighten. Another misconception is that storming is always visible and loud; some teams experience quiet resistance or disengagement instead. A third misconception is that performing is a permanent state. Even high-performing teams can fall back into storming when trust is disrupted or a dominant personality leaves.
The model can also be misused as a label. A project manager might dismiss a team's ongoing dysfunction by saying it is just storming, when the behavior is actually bullying, systemic skill gaps, or a fundamentally incompatible team structure. The model describes common phases; it does not excuse harmful behavior. Another pitfall is forcing team-building activities at the wrong stage. Team-building during forming can be useful, but during storming it may feel artificial if the real issues are unresolved role conflicts or technical disputes.
When Rigid Application of Forming Storming Norming Performing Adjourning Fails
Rigid application becomes problematic with very short teams, ongoing operational groups, large programs with multiple subteams, and heavily matrixed environments where membership rotates constantly. In these contexts, the stages may overlap, skip, or appear in radically compressed form. The model should not be used as a checklist that dictates exactly what a team must experience. If a team reaches performing without visible storming, that does not necessarily mean it avoided conflict; it may mean the conflict was handled privately or the team had unusually high psychological safety from the start. Practitioners often observe that the model is most valuable when held lightly.
Relationship to Other Project Management Concepts
The relationship between Forming Storming Norming Performing Adjourning and team development tools is most visible in the use of team charters, ground rules, and responsibility assignment matrices. A team charter established during forming can reduce storming by clarifying purpose, values, and decision rights. Ground rules support norming by naming acceptable behavior. A responsibility assignment matrix such as RACI helps resolve role ambiguity that otherwise fuels conflict. Conflict resolution techniques, from collaboration to compromise, are most relevant during storming. Delegation and servant leadership become more appropriate as the team enters performing.
The model also connects to motivation and leadership frameworks. Forming teams often need more task-oriented leadership, while performing teams can benefit from relationship-oriented and delegating styles. This mirrors situational leadership thinking, though the models are not identical. The adjourning stage connects to lessons learned and knowledge transfer, which are formal outputs in many project management methodologies. Finally, the model overlaps with risk management: team performance risk is a real threat to delivery, and recognizing early-stage patterns can inform risk responses.
Key Takeaways on Related PM Concepts
- Charters Reduce Forming Friction
- A team charter developed during the forming stage establishes a shared understanding of purpose, values, and decision rights, which lowers the intensity of disagreements that typically surface during storming.
- Ground Rules Enable Norming
- Ground rules accelerate the transition into norming by converting implicit expectations into explicit behavioral agreements that team members can hold one another accountable for.
- RACI Prevents Role Conflict
- A responsibility assignment matrix such as RACI removes the role ambiguity that commonly fuels team conflict, while collaborative and compromising conflict resolution techniques prove most effective during the storming stage.
- Leadership Styles Shift by Stage
- Teams in the forming stage generally require task-oriented direction to establish structure, whereas performing teams thrive under relationship-oriented and delegating leadership styles, reflecting the adaptive logic of situational leadership without replicating it exactly.
- Adjourning and Risk Links
- The adjourning stage provides a structured opportunity to capture lessons learned and transfer critical knowledge before the team disbands, and the associated team performance risk connects the model to formal risk management responses.
Evolution and Current Thinking
The evolution of Forming Storming Norming Performing Adjourning reflects a shift from treating the stages as fixed to using them as a diagnostic framework. Early interpretations emphasized a linear path, but contemporary research and practice acknowledge that teams cycle, regress, and sometimes never reach performing. Virtual and hybrid work have added new dimensions: storming can occur asynchronously across time zones, and forming may happen without face-to-face interaction. Psychological safety, a concept popularized by Amy Edmondson, has become an important factor in how quickly teams move from forming to performing. Teams with high psychological safety can surface disagreements earlier without the destructive edge that often characterizes storming.
Some practitioners now describe a reforming phase for project teams that reconstitute across projects, although reforming is not part of Tuckman's original model. Other frameworks, such as punctuated equilibrium and the Drexler-Sibbet Team Performance Model, offer alternative views that complicate the simple five-stage sequence. The current best practice is to use Forming Storming Norming Performing Adjourning as a shared vocabulary rather than a control mechanism. It is most effective when combined with specific observations about behavior, regular retrospectives, and a willingness to adapt leadership based on what the team is actually doing.
