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:

Know it well enough for the exam? Questions on Tuckman's Team Development Model are scenario-based, not definitional.

Practice it free

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 plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.

Burn-Up Chart

A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.

Resource Leveling

Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.

Deliverables

A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.

Power Interest Grid (Power/Influence Grid)

The power interest grid is a 2x2 stakeholder mapping tool that plots each stakeholder by power (ability to affect the project) and interest (concern about its outcome) to decide how to engage them: manage closely, keep satisfied, keep informed, or monitor.

Critical Path Method (CPM)

The Critical Path Method (CPM) is a schedule network analysis technique that calculates early and late start and finish dates for every activity to find the longest path through the project, the minimum project duration, and the float on every other path.

Weighted Shortest Job First (WSJF)

Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.

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.

Part of

Resource Management

Study full domain →

Practice Tuckman's Team Development Model

Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.