Scaling Scrum refers to the method of applying Scrum principles to large, complex projects, which often involves multiple teams. It is a critical concept for Advanced Certified ScrumMasters to understand as they help their organizations navigate the complexities of larger scale agile projects. Two notable approaches to scaling Scrum are the Scaled Agile Framework (SAFe) and Scrum of Scrums (SoS).
1. Scaled Agile Framework (SAFe)
The Scaled Agile Framework, or SAFe, is an approach that applies Scrum at an enterprise scale, supporting teams’ collaboration and delivering substantial, complex solutions.
Key concepts of SAFe include:
- Scaling Levels: SAFe organizes work at four levels: Team, Program, Large Solution, and Portfolio. Each level has a different set of roles, responsibilities, and activities.
- Program Increment (PI) Planning: SAFe involves all teams in planning sessions for the next program increment – a set number of iterations, usually between 4-6, to ensure alignment and collaboration across teams.
- Release Trains: SAFe manages dependencies through Agile Release Trains (ARTs), which are teams of agile teams working on the same solutions or product.
- Lean-Agile Mindset: SAFe emphasizes Lean-Agile principles across the entire organization, not just within teams.
Example: A large software development company uses SAFe to manage multiple interdependent teams working on a single software solution. The product is so large that it is divided into several ARTs, each managed by a Release Train Engineer (RTE), the SAFe equivalent of a Scrum Master.
SAFe | Scrum | |
Size of the project | Large, complex projects | Small to mid-sized projects |
Release Schedule | Regular release via ART | Regular release via Sprint |
Role | RTE | Scrum Master |
Planning Sessions | PI Planning | Sprint Planning |
2. Scrum of Scrums (SoS)
Another approach to scaling Scrum is the Scrum of Scrums (SoS). It is a method for coordinating multiple Scrum teams working on one project. Each Scrum team operates independently but communicates with other Scrum teams through the SoS meeting.
Key components of SoS include:
- Daily Scrum of Scrums: This meeting is similar to the Daily Scrum but includes representatives from each Scrum team that discusses progress and dependencies.
- Scrum of Scrums Master: Similar to the standard Scrum Master role, the SoS Master facilitates the SoS meetings and works to remove any obstacles identified.
- Scaling vertically and horizontally: Depending on the complexity, additional levels (Meta-Scrum, Scrum of Scrum of Scrums) could be added vertically. Simultaneously, additional teams can be added horizontally.
Example: In medium-sized software development projects, where different teams work on the distinct modules of the software, a Scrum of Scrum approach would simplify the coordination. Each Scrum team works simultaneously on their module and meets regularly in a SoS meeting, enabling better communication across the teams.
These two approaches offer different methods for scaling Scrum, each with their own strengths and weaknesses. Selecting the appropriate method depends on the size of your organization, the complexity of your projects, and the level of coordination required. As an Advanced Certified ScrumMaster, it is essential to understand these strategies to guide your organization through whichever scaling journey it undertakes.
Practice Test
True or False: One of the approaches to scaling Scrum is LeSS (Large-Scale Scrum).
- True
- False
Answer: True.
Explanation: LeSS is indeed an approach to scaling Scrum. It provides simple structural rules and guidelines on how to adopt Scrum in large scale development.
True or False: Scrum does not need dedicated techniques for scaling.
- True
- False
Answer: False.
Explanation: Scaling Scrum requires dedicated techniques to manage the complexity of coordinating multiple Scrum teams working on a large project.
Multiple Select: Which of the following are commonly recognized approaches to highly branched networks?
- A. SAFe (Scaled Agile Framework)
- B. LeSS (Large-Scale Scrum)
- C. Scrum of Scrums
- D. JAD (Joint Application Design)
Answer: A, B, C
Explanation: SAFe, LeSS, and Scrum of Scrums are recognized approaches to managing projects requiring multiple Scrum teams. JAD, however, is not designed for scaling Scrum.
True or False: In Scrum of Scrums approach, each team acts autonomously.
- True
- False
Answer: True.
Explanation: Scrum of Scrums, as one approach to scale Scrum, allows each scrum team to operate autonomously, and then synchronize their work through a ‘super standup’ meeting, or a scrum of scrums.
Single Select: Which scaling Scrum approach emphasizes coordination and synchronization among multiple teams?
- A. SAFe
- B. LeSS
- C. Scrum of Scrums
- D. DSDM
Answer: C. Scrum of Scrums
Explanation: Scrum of Scrums relies on a ‘super standup’ where representatives of each team coordinate and synchronize their work.
True or False: The Agile Manifesto directly addresses approaches to scaling Scrum.
- True
- False
Answer: False.
Explanation: The Agile Manifesto sets forth general principles for Agile development, but does not directly address specifics of scaling Scrum.
Single Select: Which scaling Scrum approach is based on Lean manufacturing principles?
- A. SAFe
- B. LeSS
- C. Scrum of Scrums
- D. DSDM
Answer: B. LeSS
Explanation: LeSS is based on Lean thinking and principles.
True or False: All Scrum scaling approaches require the same role definitions and ceremonies as standard Scrum.
- True
- False
Answer: False.
Explanation: While most approaches retain key elements of Scrum, they do not always retain exact role definitions and ceremonies due to the need to manage more complex, multi-team projects.
Multiple Select: Which of these statements are included in the principles behind the Agile Manifesto?
- A. Individuals and interactions over processes and tools
- B. Following a plan over responding to change
- C. Collaboration over negotiation
- D. Contract negotiation over customer collaboration
Answer: A, C
Explanation: The Agile Manifesto emphasizes individuals and interactions over processes and tools, and values customer collaboration over contract negotiation.
True or False: The Nexus Framework is an approach to scaling Scrum that was developed by Ken Schwaber, one of the co-creators of Scrum.
- True
- False
Answer: True.
Explanation: The Nexus Framework is indeed an approach to scaling Scrum and was developed by Ken Schwaber. It extends Scrum by adding new roles and artifacts to manage dependencies between teams.
Interview Questions
What is Scrum scaling?
Scrum scaling is the process of applying the Scrum framework to large and complex projects. It involves maintaining a consistent approach to Scrum methodologies while adapting to the requirements of a larger team or project.
Name two recognized approaches to scaling Scrum.
Two recognized approaches to scaling Scrum are the Scaled Agile Framework (SAFe) and Large Scale Scrum (LeSS).
Briefly explain the Scaled Agile Framework (SAFe) approach to scaling Scrum.
The Scaled Agile Framework (SAFe) focuses on aligning the efforts of multiple Scrum teams toward common enterprise goals. It offers a structure that facilitates communication and collaboration across multiple teams to ensure effective project delivery across a large enterprise.
What is the Large Scale Scrum (LeSS) approach to scaling Scrum?
Large Scale Scrum (LeSS) is an approach that applies basic Scrum principles to a larger team with a focus on simplicity in scaling. Though multiple teams are involved in the project, LeSS aims to keep the overall structure simple and flexible.
How does SAFe sustain workflow integration among different teams?
In the SAFe approach, workflow integration is sustained through a set of synchronized iterations, known as ‘Program Increments’. A Program Increment is a timeframe during which multiple Scrum teams work together to provide an integrated, potentially shippable product increment.
How does LeSS handle product backlog management in multi-team environments?
In LeSS, there is only one product backlog, not a separate one for each team. The Product Owner manages the entire product backlog, and teams have the autonomy to pull their work from it during Sprint Planning.
What is the key difference between the SAFe and LeSS approaches to scaling Scrum?
The key difference lies in the structured versus flexible approach. SAFe provides a more structured approach with defined roles and processes at various levels, while LeSS emphasizes more on simplifying the process and giving more autonomy to the teams.
What roles does the SAFe methodology introduce for scaling Scrum?
SAFe introduces new roles including the Release Train Engineer (RTE), System Architect, Product Management, and Business Owners to successfully scale Scrum in a larger enterprise.
How does LeSS ensure effective coordination among various Scrum teams?
In LeSS, coordination is ensured through co-located teams, shared events like the Overall Product Backlog Refinement and Overall Retrospective, and communities of practice.
What is the ‘Coordination’ level in the Large Scale Scrum framework?
The ‘Coordination’ level represents how multiple Scrum teams can work together effectively. They coordinate with each other through shared events and artifacts, face-to-face communication, and communities practice.
How does the SAFe approach manage dependencies between teams?
SAFe uses a Program Board to visualize and manage inter-team dependencies. Any dependencies are made visible and resolved proactively to minimize the negative impact on delivery.
In LeSS, how can a Product Owner effectively manage a single product backlog with multiple teams?
In LeSS, the Product Owner benefits from the support of a team of ‘Area Product Owners’ who are specialists in different areas of the product. They collectively manage the single product backlog, allowing for effective management across multiple teams.
What event in the SAFe approach is used for inspecting and adapting at the program level?
The ‘Inspect and Adapt’ (I&A) event is used in SAFe for inspecting and adapting at the program level. It provides an opportunity for multiple Scrum teams to reflect on their progress and make necessary adjustments to increase efficiency.
What kind of projects are suited for the LeSS approach of scaling Scrum?
The LeSS approach to scaling Scrum is suitable for larger, complex projects where there is a high degree of interdependence between the teams, and there is a need for increased collaboration and flexibility.
How does the SAFe approach handle portfolio management?
SAFe handles portfolio management through a Lean Portfolio Management function. This function provides strategic direction and funding, fosters Agile portfolio operations, and builds development ecosystems.