Team & agility

What Scrum team size — and how it feels inside

Lucian Katzbach Gamification designer & startup coach

10 August 2025Published

6 minReading time

At the whiteboard the question of the right SCRUM team size: three, six and nine people drawn as circles, below them close, balanced and complex

Introduction — the invisible metric for Scrum success

According to the Scrum Guide, Scrum teams should have between 3 and 9 members.

That sounds like a harmless guideline — until you have worked in all three orders of magnitude.

I have seen teams so small that in the daily you already knew what the others were going to say — and teams so large that the daily traded more small talk than progress.

I have seen how team size influences everything: from the mood in the retro to the likelihood that a story gets finished on time.

And it does not hang on the number alone. Whether people are T-shaped (broadly capable with one core competence) or pure specialists makes the difference between a team being flexible and resilient —

or sinking into chaos with every absence.

Let us dive into three everyday scenes:

A small 3-person team
A solid 6-person team
A large, globally distributed 9-person team

The characters are the same — only the team size changes.

Everyone works remotely, using Jira for tickets, Slack for chat and Teams for meetings.

The characters

On the screen the nine team members with their names: Lena, Tom, Priya and Max in the top row, Sara, Diego, Jin, Nadia and Omar below

Lena — product owner, structured, loves clear sprint goals
Tom — senior dev, T-shaped, brings humour and experience
Priya — QA engineer, finds every bug, always
Max — frontend dev, creative, sometimes chaotic
Sara — backend dev, specialised in databases, analytical
Diego — DevOps, loves automation, hates manual steps
Jin — junior dev, motivated, learns fast
Nadia — backend dev, calm, precise, loves clean code
Omar — data engineer, analytical, rather quiet, but on target in meetings

Scenario 1: the 3-person team — closely bound, but fragile

Team members: Lena, Tom, Priya

Just before the daily

Daily in the three-person team: three people in the room, one colleague joining remotely, on the board the three questions of the daily Scrum and a note about a flaky test; the board carries a red risk entry about the failing payment API test

08:57.

Slack blinks. Priya sends a GIF of a cat staring desperately at the clock.

"Daily in 3 min — and my tests are still red 🙈", she writes.

Tom is already in the Teams call. Camera on, coffee in hand.

Lena joins: "Morning you two — short and snappy today, right?"

In the 3-person team it is always snappy. Everyone knows what the others are doing.

Sometimes that can be almost too much closeness — you know the blockers, but also every frustration of the others.

How the sprint went

The sprint board shows a blocked story, triggered by a changed external interface; beside it notes on the effects of the blocker and the decision to push two stories into the next sprint

Day 3: A story escalates. An external API provider has changed its interface.

Tom has to rebuild everything.

Priya stops her tests to help — her own ticket is on ice.

The sprint goal? Already at risk.

Day 5: Lena moves two stories to "next sprint".

Nobody is surprised. But it still feels like a defeat.

Sprint Planning

It takes 20 minutes.

Lena: "We have 4 tickets we could start — but please only one at a time."

Tom and Priya nod. They know: if something escalates again, the sprint is done for.

How the 3-person team feels:

Close coordination, lightning-fast communication — but zero buffer.

One illness or one blocker is enough to topple the sprint goal.