The Scrum Team: One Cohesive Unit Focused on the Product Goal — Professional Scrum Master I (PSM I) Complete Exam-Ready Mastery Course

Meet the Scrum Team: Core Definition and Big Picture

Why the Scrum Team Matters

The Scrum Team is the central unit in Scrum. Many PSM I questions quietly test whether you truly understand what this team is, how it is structured, and how it works.

Canonical Definition

You must memorize this: "The Scrum Team is a cohesive unit of professionals focused on one objective at a time, the Product Goal." Every word in this sentence is exam-relevant.

Loaded Words

Key phrases: cohesive unit (one team, no sub-teams), professionals (trusted to manage their work), one objective at a time (shared focus on the Product Goal).

Link to Scrum Framework

Recall: "Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems." The Scrum Team is the group using this framework daily.

What You Will Learn

You will break down the three accountabilities, team size guidance, and common exam traps about sub-teams, hierarchies, and reporting lines, always tying back to empiricism and value.

Inside the Scrum Team: Three Accountabilities, One Team

Three Accountabilities

The Scrum Team has three accountabilities: Product Owner, Scrum Master, and Developers. These describe responsibilities in the framework, not necessarily job titles in HR.

Product Owner

"The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team." They focus on value, outcomes, and ordering the Product Backlog.

Scrum Master

"The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide." They focus on the effectiveness of the Scrum Team and proper use of Scrum.

Developers

"Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint." They build the product Increment that meets the Definition of Done.

No Sub-Teams or Hierarchies

The Scrum Guide is clear: within a Scrum Team there are no sub-teams or hierarchies. One team, one Product Goal, one Product Backlog, three accountabilities.

One Objective at a Time: Product Goal and Sprint Goal

Product Goal: The Big Target

"The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against." It is the long-term objective for the product.

One Objective at a Time

The Scrum Team definition says they are focused on one objective at a time, the Product Goal. At any moment, the team should have only one Product Goal in focus.

Sprint Goal: The Step

"The Sprint Goal is the single objective for the Sprint." Each Sprint Goal is a short-term objective that moves the product toward the Product Goal.

Increments as Stepping Stones

"An Increment is a concrete stepping stone toward the Product Goal." Each Increment that meets the Definition of Done is a real, usable step toward that future state.

Exam Angle

Exam questions may tempt you with multiple simultaneous Product Goals or multiple Sprint Goals per Sprint. Those are incorrect. One Product Goal per Scrum Team, one Sprint Goal per Sprint.

Team Size and Composition: Why “10 or Fewer” Matters

Size Guidance

The Scrum Guide advises that a Scrum Team is typically 10 or fewer people, including Product Owner, Scrum Master, and all Developers.

Why Small Matters

More people means more communication paths. With 10 people there are already 45 one-to-one connections. Beyond that, alignment and collaboration become much harder.

Cohesion and Accountability

Smaller teams tend to share ownership of the Product Goal more easily and can self-manage their work without heavy coordination overhead.

Exam Scenarios

If you see a 20-person Scrum Team, the Scrum-consistent answer usually involves splitting into multiple Scrum Teams that share a Product Goal and Product Backlog.

Guidance, Not a Law

"Typically 10 or fewer" is guidance, not an absolute rule, but very large teams reduce agility and should prompt you to think about forming multiple Scrum Teams.

Example: Splitting an Oversized Scrum Team

The 18-Person Team

A bank has one Scrum Team with 18 people: 1 Product Owner, 1 Scrum Master, 16 Developers. Daily Scrums drag, cliques form, and coordination is painful.

Why This Is a Problem

At 18 people, the team is far beyond the "typically 10 or fewer" guidance. Communication paths explode and the team loses cohesion around the Product Goal.

Splitting into Two Teams

A better Scrum approach: form two Scrum Teams that share the same Product Goal and Product Backlog, each with its own Scrum Master and Developers.

Different Focus, Same Goal

For example, Team A focuses on onboarding and authentication; Team B on accounts and transactions. Both still work toward the same Product Goal.

What You Do Not Do

You do not create sub-teams inside one Scrum Team or add hierarchies like "backend lead" or "frontend lead". The split is into separate Scrum Teams, not internal silos.

Cross-Functional and Self-Managing vs Traditional Silos

Cross-Functional

A cross-functional Scrum Team has all the skills needed to create a usable Increment each Sprint. They are not forced to wait on other teams for essential work.

Self-Managing

A self-managing Scrum Team decides who does what, when, and how. They organize their own work to meet the Sprint Goal without a manager assigning tasks.

Traditional Silos

Traditional setups often have separate analysis, development, and testing departments, with work handed off between them and a manager controlling day-to-day tasks.

Exam Red Flags

If a manager assigns tasks or if the team cannot deliver a usable Increment without another team each Sprint, cross-functionality or self-management is missing.

Quick Check

Ask: Can this team deliver a Done Increment themselves? Do they decide how to do the work? If yes, they are close to the Scrum ideal of cross-functional and self-managing.

Thought Exercise: Spot the Non-Scrum Pattern

Work through these short scenarios. For each, decide whether it reflects a proper Scrum Team or a more traditional, non-Scrum pattern. Then compare with the guidance.

Scenario 1: The Task-Assigning Manager

A project manager attends the Daily Scrum. After Developers share updates, the manager assigns tasks for the day and tells people which Product Backlog items they must work on.

Your judgment: Is this a Scrum-consistent pattern? Why or why not?
Hint: Think about self-management and who should decide "who does what, when, and how".

Scenario 2: The Test Department

The Scrum Team finishes development each Sprint but sends the Increment to a separate testing department. The Increment is not potentially releasable until that department finishes their work in the next Sprint.

Your judgment: Does this team qualify as cross-functional? Why or why not?
Hint: Could they create a usable Increment themselves within the Sprint?

Scenario 3: The Dual Product Goals

A Scrum Team is told by leadership to work on two Product Goals at the same time: "Expand into the EU market" and "Launch a new premium tier". The Product Owner alternates Sprint by Sprint which goal to prioritize.

Your judgment: Is this aligned with "one objective at a time"? What risks do you see?

Reflect (write down brief notes):

Which Scrum principles are being violated in each scenario?
How would you propose improving each situation while staying within Scrum?

Use your notes later when you take the diagnostic; similar patterns will appear in scenario questions.

Quiz 1: Core Definition and Team Structure

Answer this question to check your understanding of the Scrum Team definition and structure.

Which statement best reflects the Scrum Guide 2020 view of the Scrum Team?

The Scrum Team is a group of sub-teams (analysis, development, testing) managed by the Scrum Master to achieve multiple Product Goals.
The Scrum Team is a cohesive unit of professionals focused on one objective at a time, the Product Goal, with no sub-teams or hierarchies within it.
The Scrum Team is the group of Developers who implement work items assigned by the Product Owner and project manager.
The Scrum Team is any group of people working on a project, regardless of how they are organized or what their focus is.

Show Answer

Answer: B) The Scrum Team is a cohesive unit of professionals focused on one objective at a time, the Product Goal, with no sub-teams or hierarchies within it.

The Scrum Guide 2020 states: "The Scrum Team is a cohesive unit of professionals focused on one objective at a time, the Product Goal." It also clarifies there are no sub-teams or hierarchies within the Scrum Team. The other options introduce sub-teams, external managers assigning work, or ignore the focus on the Product Goal.

Quiz 2: Team Size and Self-Management

Test your understanding of size guidance and self-management.

A company has a Scrum Team of 17 people. Daily Scrums are chaotic, and a line manager assigns tasks to each Developer every morning. From a Scrum perspective, what is the BEST advice?

Keep the team as is but have the Scrum Master assign tasks instead of the line manager.
Split into multiple Scrum Teams around the same Product Goal and coach leadership to allow the teams to self-manage their work.
Appoint team leads inside the Scrum Team (frontend lead, backend lead) to coordinate and assign tasks to sub-teams.
Reduce the team to 3 people so communication is easy, and have the Product Owner directly manage their daily work.

Show Answer

Answer: B) Split into multiple Scrum Teams around the same Product Goal and coach leadership to allow the teams to self-manage their work.

Scrum suggests a Scrum Team is typically 10 or fewer people. At 17, communication and coordination are difficult. The best Scrum-aligned advice is to form multiple Scrum Teams that share the same Product Goal and Product Backlog, while also reinforcing self-management (the team, not a manager, decides who does what, when, and how). The other options keep or add hierarchies and manager-driven task assignment.

Flashcards: Key Scrum Team Concepts

Use these flashcards to reinforce the canonical definitions and core ideas about the Scrum Team.

Scrum (definition): Scrum: "Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems."
Scrum Team (definition): Scrum Team: "The Scrum Team is a cohesive unit of professionals focused on one objective at a time, the Product Goal."
Product Owner (definition): Product Owner: "The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team."
Scrum Master (definition): Scrum Master: "The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide."
Developers (definition): Developers: "Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint."
Product Goal (definition): Product Goal: "The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against."
Sprint Goal (definition): Sprint Goal: "The Sprint Goal is the single objective for the Sprint."
Increment (definition): Increment: "An Increment is a concrete stepping stone toward the Product Goal."
Scrum Team size guidance: A Scrum Team is typically 10 or fewer people, including the Product Owner, Scrum Master, and Developers. Larger groups should usually be split into multiple Scrum Teams.
No sub-teams or hierarchies: Within a Scrum Team there are no sub-teams or hierarchies. There is one team with three accountabilities: Product Owner, Scrum Master, and Developers.
Cross-functional team: A cross-functional Scrum Team has all the skills necessary to create a usable Increment each Sprint without depending on other teams for core work.
Self-managing team: A self-managing Scrum Team decides internally who does what, when, and how, instead of having tasks assigned by an external manager.

Common Exam Traps: Sub-Teams, Reporting Lines, and Titles

Trap 1: Sub-Teams

Phrases like "testing sub-team" or "frontend sub-team" inside one Scrum Team are a red flag. Scrum specifies no sub-teams or hierarchies within the Scrum Team.

Trap 2: Task Assignment

If a manager or Scrum Master assigns tasks to Developers, self-management is broken. The Scrum Team should decide who does what, when, and how.

Trap 3: Many Product Owners

One Scrum Team should have one Product Owner. Multiple Product Owners for a single Scrum Team usually signals confusion and diluted accountability.

Trap 4: Titles vs Accountabilities

Ignore corporate titles like "Business Analyst" or "Tech Lead" in exam scenarios. Map people to Product Owner, Scrum Master, or Developers based on what they actually do.

Your Mental Checklist

Ask: Is this one cohesive Scrum Team, with one Product Goal, no internal hierarchies, cross-functional skills, and self-management? If not, look for the answer that restores these.

Apply It: Mini Scenario Walkthrough

Use this short scenario to practice thinking like the exam.

Scenario: The Reporting Scrum Master

A company has a Scrum Team of 9 people:

1 Product Owner
1 Scrum Master
7 Developers

The Scrum Master reports to the Head of Delivery, who insists that:

The Scrum Master must approve all changes to the Sprint Backlog.
The Scrum Master must provide a weekly report on each Developer’s individual productivity.

The Scrum Master starts telling Developers which tasks they should pick up to ensure "balanced utilization".

Questions (write down your answers):

Which Scrum principles or characteristics are being violated here?

Hint: Think about self-management and the purpose of the Sprint Backlog.

In Scrum, who owns the Sprint Backlog and decides how to turn selected Product Backlog items into a usable Increment?
What would be a more Scrum-consistent behavior for the Scrum Master in this situation?

Suggested reasoning path:

Recall that the Sprint Backlog is owned by the Developers. "The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how)." The Developers create and adapt this plan.
Self-managing teams decide who does what, when, and how. A Scrum Master assigning tasks undermines this.
A Scrum Master should focus on coaching, removing impediments, and improving the team’s use of Scrum, not on controlling people.

Compare your answers with this reasoning. This is the style of thought the upcoming mock exam will pressure-test.

Key Terms

Scrum: Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.
Increment: An Increment is a concrete stepping stone toward the Product Goal.
Developers: Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint.
Empiricism: Scrum is founded on empiricism and lean thinking.
Scrum Team: The Scrum Team is a cohesive unit of professionals focused on one objective at a time, the Product Goal.
Sprint Goal: The Sprint Goal is the single objective for the Sprint.
Product Goal: The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against.
Scrum Master: The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide.
Product Owner: The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team.
Sprint Backlog: The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how).
Product Backlog: The Product Backlog is an emergent, ordered list of what is needed to improve the product.
Definition of Done: The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product.
Self-managing team: A team that decides internally who does what, when, and how, instead of having tasks assigned by an external manager.
Team size guidance: In Scrum, a Scrum Team is typically 10 or fewer people, including the Product Owner, Scrum Master, and Developers.
Cross-functional team: A team that has all the skills needed to deliver a usable Increment each Sprint without relying on other teams for core work.