Team and Resources · tool 3 of 5
Team Development Stages
Team Development Stages: explains why new teams struggle and what they need at each stage.
Best for: Forming or changing a team · Time: Reference
Domain: Resources · Focus area: Executing
How it works
Bruce Tuckman described forming, storming, norming and performing, and later adjourning. Teams can go back a stage when people join or goals change.
- Forming: give clarity.
- Storming: surface and resolve conflict.
- Norming and performing: step back and support.
How to apply it
- Spot the stage.
- Adjust your style.
- Expect a dip after any change.
- Mark the end properly.
In practice
Two new engineers join a settled team, and arguments return. That’s storming again, not failure.
Pro tip
Storming isn’t a warning sign. Teams that skip it usually just hide the conflict.
Quick check
A settled team gets two new members and tension returns. What’s happening?
Sources
- B. Tuckman, “Developmental Sequence in Small Groups”, Psychological Bulletin (1965); Tuckman and Jensen (1977)
Last reviewed 2026-11-02 against the PMBOK® Guide, 8th edition · Practitioner review pending · How this guide is made