The stage Tuckman skipped

The team that agrees to everything and owns nothing

Every working agreement is signed. Every retro format is followed. Every sprint goal is technically accepted. And yet by the second month, the working agreements are being gently ignored, the retro format is going through the motions, and the sprint goals are being executed with the minimum of genuine investment.

The problem is not disengagement. It is that the team never reached the developmental stage where genuine commitment forms. They got to compliance — and compliance is not the same thing.

Why Tuckman doesn't fit agile teams

Tuckman's forming-storming-norming-performing model is one of the most cited frameworks in team development and one of the least examined. Tuckman's 1965 review synthesised over fifty studies — but almost all of them involved groups with passive, non-directive leaders: therapy groups, training groups, sensitivity groups where the coordinator deliberately did not intervene in the process.

In those groups, storming is unmanaged rebellion. Nobody intercepts it, reframes it, or facilitates it toward a productive outcome. It plays out, and then the group either finds its own norms or it doesn't.

Agile teams are not passive-leader groups. They have Scrum Masters, coaches, delivery leads, and a calendar full of structured ceremonies. When rebellion surfaces — when someone challenges the sprint goal framing or refuses a working agreement — it is almost always intercepted: smoothed, reframed, or quietly pressured back into compliance. The storming stage gets managed away before it can do its developmental work.

The seven-stage model

Johnson and Johnson's seven-stage model was developed specifically for task-focused groups with active coordinators — closer to the conditions of an agile team than anything Tuckman reviewed. It distinguishes two stages that Tuckman treats as continuous: conforming (stage 2) and committing (stage 5). Between them sits the stage that Tuckman merges into storming and norming — and that agile coaches most often suppress.

What the rebellion stage looks like in agile teams

In the J&J model, stage four is described as rebelling and differentiating. Members assert their individual perspectives, challenge imposed norms, and resist the coordinator's authority — not as dysfunction, but as the developmental act through which genuine ownership becomes possible. The key word is differentiating: members cannot own something they have not first had the opportunity to push against.

In agile teams, the rebellion stage often looks like this:

Each of these can look like resistance, low engagement, or difficult personality. Most coaches respond by facilitating toward agreement. That response is understandable. It is also what prevents the team from reaching stage five.

What happens when rebellion is suppressed

When the rebellion stage is smoothed before it runs its course, teams produce pseudo-commitment: agreement that persists as long as conditions are stable and evaporates as soon as pressure rises. Working agreements are followed in the presence of the coach and gently discarded without them. Sprint goals are accepted without ever becoming genuinely wanted.

The pattern looks stable from the outside. It has no tensile strength because it was never negotiated — only accepted. The team moved from conforming (stage 2) to a permanent version of conforming that looks like the mature stage but lacks its depth.

Rebellion vs genuine dysfunction

Not everything that looks like rebellion is developmental. The diagnostic question is whether the challenge is aimed at a process or a person, at an imposed norm or at the team's existence itself.

Coaching through the rebellion stage

The coach's task at stage four is to accept rather than smooth. That means naming the differentiation as legitimate: "It sounds like you want this to work differently than we've set it up — say more about that." It means using integrative conversation (what can we negotiate here?) rather than consensus pressure (can we find something everyone agrees with?).

Three things to avoid at this stage: retro formats that structure the conversation toward agreement before the disagreement has been heard; team charters written in the forming stage and presented as settled when they haven't been tested; norms imposed by the coach or process rather than negotiated by the members themselves.

The rebellion stage is not a problem the coach needs to solve. It is the developmental act through which the team moves from following the process to owning it. Suppressing it doesn't prevent conflict — it stores it.