Skip to content
PMPCAPM

Tuckman's Team Development Model

Tuckman's model describes five stages of team development: forming, storming, norming, performing, and adjourning. Teams progress through these stages as they mature and develop working relationships.

Share:

Explanation

Developed by Bruce Tuckman in 1965 (with the adjourning stage added in 1977), this model provides a framework for understanding how teams evolve over time. The stages are forming (team assembles and learns about the project), storming (conflicts emerge as team members assert their perspectives), norming (the team establishes working norms and begins collaborating effectively), performing (the team functions as a well-organized unit achieving high performance), and adjourning (the team completes the work and disbands).\n\nTeams do not always progress linearly through these stages. A team may regress to an earlier stage when new members join, when leadership changes, or when significant conflicts arise. The project manager's leadership style should adapt to the team's current stage — more directive during forming and storming, more facilitative during norming and performing.\n\nUnderstanding this model helps project managers set realistic expectations for team performance, recognize signs of team progression or regression, and apply appropriate interventions. For example, conflict during the storming stage is normal and should be managed constructively rather than avoided.

Key Points

  • Five stages: Forming, Storming, Norming, Performing, Adjourning
  • Teams may regress to earlier stages with changes in membership or context
  • Project manager leadership style should adapt to the current stage
  • Conflict during storming is normal and expected

Exam Tip

Tuckman's model is heavily tested. Memorize the five stages in order and know the characteristics of each. Expect scenario questions asking you to identify which stage a team is in.

Frequently Asked Questions

Related Topics

High-yield topics our learners drill most before exam day.

Burndown Chart

A Burndown Chart is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.

Resource Leveling

Resource leveling is a resource optimization technique in which adjustments are made to the project schedule to keep resource usage at or below a defined limit, often resulting in a longer project duration.

Risk Register

The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.

Stakeholder Mapping

Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.

Relative Estimation

Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.

Cost Performance Index (CPI)

Cost Performance Index (CPI) is an EVM efficiency metric that measures cost performance as the ratio of earned value to actual cost: CPI = EV / AC.

Schedule Performance Index (SPI)

Schedule Performance Index (SPI) is an EVM efficiency metric that measures schedule performance as the ratio of earned value to planned value: SPI = EV / PV.

Earned Value Management (EVM)

Earned Value Management (EVM) is a methodology that integrates scope, schedule, and cost data to assess project performance and progress objectively.

Power/Influence Grid

The power/influence grid is a stakeholder classification model that groups stakeholders based on their level of authority (power) and their active involvement or ability to affect the project (influence).

Part of

Resource Management

Study full domain →

Test your knowledge

Practice scenario-based questions on this topic with detailed explanations.