The Scrum Team: No Hierarchies

Overview

• What you’ll learn: The structure and composition of a Scrum Team, why there are no hierarchies, the concept of accountabilities vs. roles, and the ideal team size.
• Prerequisites: Module 1 — Agile Foundations (Lessons 1–8).
• Estimated reading time: 14 minutes

Introduction

Traditional organizations love hierarchy. There is a project manager, a team lead, a senior developer, a junior developer, and someone who fetches coffee. Everyone knows their place, and decisions flow downward like water through a bureaucratic waterfall.

Scrum says: no. The Scrum Team is a flat, self-managing unit of professionals who collectively own the responsibility for delivering value. There are no sub-teams, no hierarchies, and no one telling anyone else what to do. Instead, there are three specific accountabilities: Product Owner, Scrum Master, and Developers.

Note the word “accountabilities,” not “roles.” The 2020 Scrum Guide deliberately changed this language. A role implies a job title; an accountability implies ownership. You are not just playing a part — you are responsible for outcomes.

The Scrum Team Composition

A Scrum Team consists of exactly one Product Owner, one Scrum Master, and Developers. The entire team is accountable for creating a valuable, useful Increment every Sprint.

Why No Hierarchies?

• Faster decisions: When the team does not need to escalate every choice, decisions happen at the speed of conversation rather than the speed of email chains.
• Shared ownership: Without a single “boss” to blame, the team collectively owns successes and failures. This creates genuine accountability.
• Cross-functionality: The team has all the skills needed to create value each Sprint. No dependencies on external teams or approvals.
• Self-management: The team decides who does what, when, and how. They are the experts; trust them to organize their own work.

Team Size

The Scrum Guide recommends that the Scrum Team be small enough to remain agile and large enough to complete significant work. Typically, 10 or fewer people. If teams become too large, they should consider reorganizing into multiple cohesive Scrum Teams, each focused on the same product — sharing the same Product Goal, Product Backlog, and Product Owner.

Why Small Teams Work Better

• Communication channels: A team of 5 has 10 communication channels. A team of 10 has 45. A team of 15 has 105. Complexity grows quadratically.
• Coordination cost: The larger the team, the more time spent synchronizing and the less time spent building.
• Social loafing: In larger groups, individuals tend to contribute less because they assume others will pick up the slack.

Accountabilities, Not Roles

The shift from “roles” to “accountabilities” in the 2020 Scrum Guide was deliberate. A role suggests a job description; an accountability suggests ownership of outcomes.

• The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team.
• The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide and for the Scrum Team’s effectiveness.
• The Developers are accountable for creating any aspect of a usable Increment each Sprint.

One person can hold one accountability. The Product Owner is one person, not a committee. The Scrum Master is one person. But a person may serve as both a Developer and a Scrum Master, or even (though not recommended) a Developer and a Product Owner — as long as the accountabilities are clearly understood.

Key Takeaways

• The Scrum Team is flat — no hierarchy, no sub-teams, no titles beyond the three accountabilities.
• Three accountabilities: Product Owner, Scrum Master, Developers. Not roles — accountabilities.
• Teams should be 10 or fewer people. Larger teams should split into multiple Scrum Teams sharing the same product.
• Self-management means the team decides who does what, when, and how.
• Cross-functionality means the team has all skills needed to deliver value each Sprint.

What’s Next

In Lesson 10, you will explore the Product Owner accountability — the person responsible for maximizing the value of the product and managing the Product Backlog.