The Definitive Guide to Scrum at Scale Scrum, as originally outlined in the Scrum Guide, is a framework for developing, delivering, and sustaining complex products by a single team. Since its inception, it’s usage has extended to the creation of products, processes, services, and systems that require the efforts of multiple teams. Scrum@Scale was created to efficiently coordinate this new ecosystem of teams. It achieves this goal through setting up a “minimum viable bureaucracy” via a “scale-free” architecture.
Purpose of the Scrum@Scale Guide
This guide provides the definition of Scrum@Scale and the components of its framework. It explains the scaled roles, scaled events, and enterprise artifacts, as well as the rules that bind them together.
This guide is broken down into four basic sections:
an introduction to Scrum@Scale, with the basics for getting started
an overview of the Scrum Master Cycle
an overview of the Product Owner Cycle
a walk-through of bringing the cycles together
Each component serves a specific purpose which is required for success at scale. Changing their core design or ideas, omitting them, or not following the base rules laid out in this guide limits the benefits of Scrum@Scale.
Specific tactics beyond the basic structure and rules for implementing each component vary and are not described in this Guide. Other sources provide complementary patterns, processes, and insights.
The Components of Scrum@Scale
Agenda
Preface to the Scrum@Scale Guide
Purpose of the Scrum@Scale Guide
Definitions
The Components of Scrum@Scale
Values-Driven Culture
Getting Started: Installing an Agile Operating System
Scaling The Teams
The Team Process
The Scrum of Scrums (SoS)
Scaling in Larger Organizations
Scaling the Events and Roles
Event: The Scaled Daily Scrum (SDS)
Event: The Scaled Retrospective
The Scrum Master Cycle: Coordinating the “How”
Role: The Scrum of Scrums Master (SoSM)
The Hub of the SM Cycle: The Executive Action Team (EAT)
EAT Backlog and Responsibilities
Continuous Improvement and Impediment Removal
Cross-Team Coordination
Delivery
The Product Owner Cycle: Coordinating the “What”
Scaling the Product Owner – The Product Owner Cycle
Role: The Chief Product Owner (CPO)
Scaling the Product Owner Team
The Hub of the PO Cycle: The Executive MetaScrum (EMS)
Coordinating the “What” – The Product Owner Cycle
Strategic Vision
Backlog Prioritization
Backlog Decomposition and Refinement
Release Planning
Connecting the Product Owner and Scrum Master Cycles
Product Feedback and Release Feedback
Metrics and Transparency
Some Notes on Organizational Design
Why Should Employees Become Scrum@Scale Practitioners?
The Scrum@Scale® course teaches the responsibilities of the Product Owner, individual Scrum teams, and enterprise leadership in a variety of large-scale contexts. In this course, students will learn the following:
Overcome the challenges of cross-team dependencies with an emphasis on prioritization at the enterprise level
Refactor organization to meet changing market demands
Deliver working product on a regular cadence
Facilitate cross-team collaboration and release planning with one to many teams across any sized initiative
Develop a transformation backlog to scale organizational reach and impact
Measure and improve key metrics for Enterprise agility
Deliver twice the business value at half the cost
Who Should Take a Scrum@Scale Practitioner Course?
The Scrum@Scale® course teaches the responsibilities of the Product Owner, individual Scrum teams, and enterprise leadership in a variety of large-scale contexts.
This course is for anyone interested in how Scrum can be used to reform organizations to deliver twice the value in half the time.
This course will help leaders and employees to become agile change agents at scale.
This course will help managers start Agile transformations.
This course will help managers lead and empower Scrum teams.
Get In Touch
Submit your Query, we will get back to you shortly.