SkarpChapter 9 of 10
Scrum Beyond the Basics: Scaling, Leadership, and the Organization
See how Scrum behaves when multiple teams, managers, and organizational constraints come into play, and learn how to pick the answer that matches Scrum.org’s lean, minimalistic stance.
Scrum Beyond One Team: What Changes, What Stays the Same
Module Focus
You will explore how Scrum behaves with multiple teams, managers, and organizational constraints, while staying aligned with the Scrum Guide 2020 and Scrum.org exam style.
Scrum.org Exam Lens
For PSM I, assume minimal roles, artifacts, and events. Extra layers from scaling frameworks are optional add-ons, not part of core Scrum.
Thinking Strategy
When in doubt, ask: What does the Scrum Guide say? How can multiple teams apply that without inventing mandatory new roles or events?
Learning Goals
You will learn to pick minimal, Scrum-Guide-compliant answers, and to see the Scrum Master as a change agent working with leadership and the wider organization.
Multi-team Scrum: One Product, One Product Backlog
Core Rule
With multiple teams on one product, Scrum still has one Product Owner, one Product Backlog, and one Product Goal at a time.
No Separate Backlogs
Teams do not get their own official Product Backlogs for the same product. They may use views or filters, but the artifact stays single.
Exam Signal
Options like "one Product Backlog per team for the same product" or "one Product Owner per team" contradict the Scrum Guide.
Visual Picture
Picture one ordered Product Backlog. Several teams pull different items from this same list during Sprint Planning, all serving the same Product Goal.
Example: Three Teams, One Product Backlog
Scenario Setup
One mobile banking app, three Scrum Teams, each with its own backlog and "Product Owner". Work overlaps, releases slip, and customers see inconsistencies.
Step 1–3 Fix
Define the app as one product, appoint one Product Owner, and merge the three backlogs into a single ordered Product Backlog owned by that Product Owner.
Step 4–5 Fix
Set a clear Product Goal. In multi-team Sprint Planning, the Product Owner presents top items, and each team selects work and crafts its own Sprint Goal.
Exam Takeaway
Prefer answers that keep one Product Owner and one Product Backlog for the app, with multiple teams creating their own Sprint Goals aligned to the Product Goal.
Scaling Events: Keep Scrum Events, Add Only When Necessary
Events Stay the Same
Even with many teams, the core events remain: Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective.
Team-Level Ownership
Each Scrum Team keeps its own Daily Scrum, Planning, Review, and Retrospective. Extra coordination events are optional.
Exam Traps
The Scrum Guide does not define Scrum-of-Scrums or Release Train Engineers. Those belong to specific scaling frameworks, not to Scrum itself.
Recognizing Good Answers
Prefer answers that keep the five Scrum events and allow teams to add coordination meetings as adaptations, not as mandatory parts of Scrum.
Thought Exercise: Choosing the Lean Scaling Option
Read the situation and decide which approach best matches Scrum.org's lean stance.
Situation:
- Four Scrum Teams work on the same web platform.
- They struggle with dependencies and overlapping work.
You see three proposed actions:
- Create a mandatory Scrum-of-Scrums event defined as a new Scrum event, with a new "Chief Scrum Master" role.
- Ask the teams to experiment with a short, optional cross-team sync after their Daily Scrums, while keeping all existing Scrum events.
- Replace each team’s Daily Scrum with a single big Daily Scrum for all four teams.
Your task:
- Rank these from most aligned to least aligned with Scrum.org’s view.
- Write down your ranking and a one-line reason for each.
Suggested solution (check after you think):
- Most aligned: 2
- Uses empiricism and small adaptations, keeps core Scrum events, adds no new mandatory roles.
- Next: 3
- Keeps a Daily Scrum, but weakens self-management and focus by creating a large meeting; not ideal, but still within the Guide if teams choose it.
- Least aligned: 1
- Adds a new role and declares a new mandatory Scrum event; conflicts with the minimal, framework-neutral Scrum Guide.
Scrum Master and Management: Removing Organizational Impediments
Scrum Master’s Wider Role
Beyond the team, the Scrum Master serves the organization by leading, training, and coaching in Scrum, and by helping with Scrum adoption.
Organizational Impediments
Impediments include policies against self-management, siloed departments, slow approvals, and performance systems that block team-based work.
Change Agent Actions
The Scrum Master makes impediments visible, works with leadership, coaches rather than commands, and supports small, sustainable experiments.
Exam Perspective
Prefer answers where the Scrum Master collaborates with management, educates them, and focuses on removing impediments, not on acting as a project manager.
Example: Scrum Master Coaching Leadership
Scenario
Three Scrum Teams share a product, but managers still assign tasks, approve every backlog item, and measure individuals by hours worked.
Step 1–2: Evidence and Education
The Scrum Master gathers data on delays and explains self-management, the Product Owner’s role, and the true purpose of the Daily Scrum.
Step 3–4: Experiments and Adaptation
They propose small experiments: Developers pull work, approvals are reduced, managers attend Reviews. After a few Sprints, leadership inspects results and adapts policies.
Exam Takeaway
Look for answers where the Scrum Master coaches and partners with leadership to change structures, instead of accepting command-and-control or acting as a project manager.
Quiz: Minimal Roles in Multi-team Scrum
Check your understanding of roles when multiple teams work on one product.
Several Scrum Teams work on the same product. Which option best reflects Scrum.org’s stance on roles?
- Appoint one Chief Product Owner over several Product Owners, one for each team.
- Keep one Product Owner for the product and multiple Scrum Teams sharing one Product Backlog.
- Create a new role, the Program Manager, to coordinate all Product Owners and Scrum Masters.
- Have each team select its own Product Owner so decisions can be made locally.
Show Answer
Answer: B) Keep one Product Owner for the product and multiple Scrum Teams sharing one Product Backlog.
The Scrum Guide defines one Product Owner per product, accountable for maximizing value and managing a single Product Backlog. Multiple Scrum Teams may share this Product Owner and Product Backlog. Chief Product Owners, Program Managers, or one Product Owner per team for the same product are outside core Scrum.
Quiz: Events and Scaling
Test how well you can spot Scrum.org-friendly answers about events.
Four Scrum Teams work on one product and struggle with dependencies. Which action is most consistent with the Scrum Guide and Scrum.org’s lean stance?
- Introduce a mandatory Scrum-of-Scrums event defined as the sixth official Scrum event.
- Ask the teams to experiment with a brief cross-team sync after their Daily Scrums, keeping all existing Scrum events.
- Replace all teams’ Sprint Reviews with a single monthly steering committee meeting.
- Cancel individual team Retrospectives and hold only a big, quarterly organizational retrospective.
Show Answer
Answer: B) Ask the teams to experiment with a brief cross-team sync after their Daily Scrums, keeping all existing Scrum events.
The Scrum Guide defines only five events. Teams may add coordination meetings as adaptations, but these are not official Scrum events. Option 2 keeps all Scrum events and uses empiricism to experiment with coordination. The other options remove or replace core Scrum events or falsely define a new official event.
Key Terms Review
Flip these cards to reinforce core ideas about scaling, leadership, and the organization in Scrum.
- One product, one Product Backlog
- In Scrum, a single product has one Product Backlog and one Product Owner. Multiple Scrum Teams can share this backlog and Product Owner.
- Multi-team Sprint Planning
- The Product Owner presents the ordered Product Backlog; each Scrum Team selects work and crafts its own Sprint Goal that supports the shared Product Goal.
- Scrum events in scaling
- Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective remain the only official Scrum events, even with many teams.
- Organizational impediment
- A structural, policy, or cultural issue in the organization that slows or prevents Scrum Teams from delivering value and self-managing.
- Scrum Master as change agent
- The Scrum Master works with leadership and the organization to make impediments visible, coach in Scrum, and support structural changes that enable empiricism.
- Scrum.org’s lean stance
- Prefers minimal roles, artifacts, and events; extra layers from scaling frameworks are optional practices, not part of the core Scrum framework.
Key Terms
- Increment
- A concrete stepping stone toward the Product Goal. It is a usable piece of product that must meet the Definition of Done.
- Empiricism
- A way of working based on transparency, inspection, and adaptation. Scrum is founded on empiricism and lean thinking.
- Sprint Goal
- A single objective for the Sprint that provides focus and guides the Developers on why they are building the Increment.
- Change agent
- A person who helps an organization move from current ways of working to more effective ones. In Scrum, the Scrum Master is explicitly a change agent.
- Product Goal
- A long-term objective for the Scrum Team. It provides a target for the Product Backlog and gives context to Sprint Goals.
- Scaling Scrum
- Using Scrum with multiple teams working on the same product. Core Scrum stays the same; additional coordination practices may be added as adaptations.
- Product Backlog
- An emergent, ordered list of what is needed to improve the product. It is the single source of work undertaken by the Scrum Team.
- Scrum-of-Scrums
- A common but non-standard coordination meeting used in some scaled environments. It is not defined or required by the Scrum Guide.
- Self-management
- The ability of the Scrum Team to internally decide who does what, when, and how, within the boundaries of the Sprint Goal and product constraints.
- Organizational impediment
- A systemic obstacle in structure, policy, or culture that limits a Scrum Team’s ability to deliver value or apply empiricism effectively.