Certified ScrumMaster (CSM) Scaling Scrum and Organizational Adoption Syllabus

Scaling Scrum and Organizational Adoption syllabus — full chapter and topic list

Expand any chapter to see its topics and sub-topics. This is the whole examinable outline for Scaling Scrum and Organizational Adoption in Certified ScrumMaster (CSM), not a summary of it.

1. 1

   Foundations of Scaling

   3 topics

   • Why Scale Scrum
     • Coordinating multiple teams on one product
     • Dependencies and integration challenges
   • Keeping Scaling Lightweight
     • Descaling before scaling
     • Avoiding unnecessary complexity
   • Cross-Team Coordination
     • Shared Product Backlog and Definition of Done
     • Integration across teams
2. 2

   Common Scaling Approaches

   3 topics

   • Nexus Framework Overview
     • Nexus Integration Team
     • Nexus events
   • Large-Scale Scrum (LeSS)
     • LeSS principles
     • One Product Owner across teams
   • Scrum of Scrums
     • Coordinating representatives across teams
3. 3

   Driving Organizational Change

   4 topics

   • Change Management Models
     • Kotter's eight steps
     • Lewin's change model
   • Overcoming Resistance
     • Addressing common objections
     • Building a coalition for change
   • Measuring Agile Adoption
     • Evidence-Based Management overview
     • Health and value metrics
   • Sustaining Continuous Improvement
     • Kaizen mindset
     • Communities of practice

Scaling Scrum and Organizational Adoption flashcards for Certified ScrumMaster (CSM)

21 of 50 cards from the Scaling Scrum and Organizational Adoption deck — real questions with worked answers.

1. What is the primary reason organizations choose to scale Scrum?

   To coordinate multiple Scrum teams working on a single large product or interdependent products so they deliver integrated, valuable increments together, since one team of 3-9 developers cannot handle the size or complexity of the work alone.

2. What signals indicate that a single Scrum team should consider scaling?

   The product is too large for one team to build in a reasonable time, work has grown beyond a 3-9 person team's capacity, there are heavy cross-component dependencies, and faster time-to-market requires parallel team effort.

3. What is the central risk of scaling Scrum, and what principle counters it?

   The risk is adding bureaucracy, extra roles, and coordination overhead. The counter-principle is 'descaling' / keeping it lightweight—add the minimum structure needed and remove organizational complexity rather than adding process.

4. What does 'keeping scaling lightweight' mean in practice?

   Preserving the core Scrum framework (roles, events, artifacts) while adding only the minimal coordination needed for multiple teams, avoiding heavyweight processes, extra hierarchy, and unnecessary new roles.

5. In scaled Scrum, what is the recommended approach to the Product Backlog across multiple teams?

   Use a single, shared Product Backlog for the whole product with one Product Owner accountable for it, rather than separate backlogs per team, to keep priorities aligned to one product vision.

6. Why is a shared 'Definition of Done' critical when multiple teams work on one product?

   It ensures all teams produce work of the same quality that integrates into a single, releasable increment; without a common DoD, integration breaks and undone work accumulates across teams.

7. What is the core purpose of cross-team coordination in scaled Scrum?

   To manage dependencies, integrate work into one common increment, share knowledge, and align teams toward a single product goal while keeping each team self-managing.

8. Name three common types of dependencies that cross-team coordination must manage.

   Technical/architectural dependencies (shared code or components), knowledge/expertise dependencies (specialized skills), and work/sequencing dependencies (one team's output is another's input).

9. What is the Scrum of Scrums (SoS)?

   A scaling technique in which representatives (often called ambassadors) from each Scrum team meet regularly to coordinate work, integrate efforts, and surface and resolve cross-team dependencies and impediments.

10. Who typically attends a Scrum of Scrums meeting?

    One ambassador/representative from each team—often a developer rather than the Scrum Master—who can speak to the team's progress and raise cross-team impediments.

11. What four questions are commonly used in a Scrum of Scrums meeting?

    What has my team done since we last met that affects other teams? What will my team do before we next meet? What impediments are in my team's way? Am I about to put something in another team's way (creating a dependency)?

12. How often is a Scrum of Scrums typically held?

    As needed for coordination—commonly several times a week (e.g., daily or 2-3 times per week)—not necessarily every day, scheduled based on how much cross-team integration is required.

13. What is the Scrum of Scrums of Scrums (meta-scrum)?

    A higher-level coordination meeting where ambassadors from multiple Scrum of Scrums groups meet, used to scale coordination across very large programs with many teams (a third tier of the SoS pattern).

14. What is the Nexus framework?

    A scaling framework created by Ken Schwaber and Scrum.org that lets 3-9 Scrum teams work together on a single Product Backlog to build one integrated increment, with the Nexus Integration Team coordinating integration.

15. How many Scrum teams does a Nexus typically contain?

    Approximately 3 to 9 Scrum teams working from one Product Backlog toward one product goal.

16. What is the Nexus Integration Team (NIT) and what is it accountable for?

    A special team in Nexus accountable for ensuring a successfully integrated increment is produced at least every Sprint; it coaches teams, identifies/resolves integration issues, and owns integration tooling and practices.

17. Who are the members of the Nexus Integration Team?

    The Product Owner (one for the whole Nexus), a Scrum Master, and Nexus Integration Team members; some members may also work on individual Scrum teams within the Nexus.

18. What new event does Nexus add at the start of the Sprint, and what is its purpose?

    Nexus Sprint Planning (and Refinement)—coordinated cross-team planning to identify dependencies, decide which team does which work, and minimize cross-team dependencies before the Sprint.

19. What is the Nexus Sprint Backlog?

    An artifact that makes the dependencies and the flow of work across all teams in the Nexus transparent, composed of Product Backlog items and the cross-team dependencies among them, at least for the current Sprint.

20. What is the Nexus Daily Scrum?

    An event where appropriate representatives from each team's Daily Scrum meet to identify integration issues and inspect progress toward the Nexus Sprint Goal, focusing on cross-team dependencies.

21. List the five Nexus events.

    Nexus Sprint Planning, Nexus Daily Scrum, Nexus Sprint Review, Nexus Sprint Retrospective, and Refinement (Nexus Refinement)—all wrapped around the standard Scrum events within the shared Sprint.

See more Scaling Scrum and Organizational Adoption flashcards →

Planning Scaling Scrum and Organizational Adoption for Certified ScrumMaster (CSM)

Scaling Scrum and Organizational Adoption (Certified ScrumMaster (CSM)) FAQ