The Scrum framework : Scaled Scrum

Scaled Scrum definition

• Scaled Scrum is based on the Scrum framework and uses Scrum parts as its building blocks with some additions or changes within which multiple Development Teams work on the same Product for one or more Sprints in order to produce a potentially releasable and usable integrated Increment at the end of each Sprint.

Scaled Scrum Teams

• In Scaled Scrum which multiple Scrum Teams work on a single Product, there is just one Product Owner, one Product Backlog, multiple Development Teams, and one Scrum Master position for each Scrum Team that can be filled with one or multiple Scrum Masters.
• Each team in Scaled Scrum should be cross-functional which means each team should have all required skills to convert Product Backlog Items to a potentially releasable and usable Increment.
• Also, they should adhere to the minimum and maximum amount of Developers in each team i.e. 3-9 members.

Scaled Scrum Roles

• In Scaled Scrum which multiple Scrum Teams work on a single Product, there is just one Product Owner, multiple Development Teams, and one Scrum Master position for each Development Team that can be filled with one Scrum Master for all Teams or multiple Scrum Masters (one by Team).

Scaled Scrum Increment

• In Scaled Scrum, each Team creates their done Increment and they integrate their work on a daily basis.
• However, the integrated Increment as a whole, which contains all Teams’ outputs is used to demonstrate in the Sprint Review.
• A Single Increment is needed at the end of the Sprint.
  • A Single Increment is needed at the end of the Sprint.
  • Regardless of the number of Teams, the Development Teams should merge their code to have one single “Releasable” Increment by the end of the Sprint.
    • Regardless of the number of Teams or the Branch they work in, the Development Teams should merge their code to have one single “Releasable” Increment (one main branch) by the end of the Sprint.

Scaled Scrum Definition of Done

• When multiple Development Teams are working on the same Product they could (not should) have one Definition of Done (DoD) for all Teams or each Team could have its own one or something between these two extremes.
• The rule here is that their outputs should be combined and integrated continuously and at the end of the Sprint they should deliver just one integrated Increment as all Teams’ output so all Definition of Done (DoD) should not violate each other.

Scaled Scrum Version control (main trunk)

• A company has multiple teams working on a single product with a single Product Backlog.
  • Continuous Integration (CI) (to trunk) is a great state to aim for.
    • Each member of the teams frequently commit their code back to the main trunk, rather than each team managing their own branch.
  • In Scaled Scrum, each Team creates their done Increment and they integrate their work on a daily basis.
  • However, the integrated Increment as a whole, which contains all Teams’ outputs is used to demonstrate in the Sprint Review.
    • All teams frequently integrate their work into a common environment that can be tested to ensure that the integration is done.

Scaled Scrum practice

• Different Teams working on the same Product :
  • One Product = One Product Backlog = One Product Owner, always !
    • One Product has exactly one Product Backlog and exactly one Product Owner, irrespective of how many Development Teams may be working on it.
  • So in Scaled Scrum, the Scrum Teams :
    • Must have the same Product Backlog
    • Must have the same Product Owner
    • Must have the same Product Goal
    • Must have different Sprint Backlogs, one for each Team
    • Must have a shared Definition of Done (DoD)
    • Can have different Sprint lenghts (but not recommended)
    • Can have different Scrum Masters or the same Scrum Master

Scaled Scrum questions and answers

• Q1: How to start a big complex project ?
  • A1 : Form 1-2 teams of best Developers for implementing the core, add more teams later.
• Q2 : A system is decomposed into elements like workflows, features, capabilities, etc. How it affects Scrum Team on a scaled project?
  • A2 : It will be reflected in the implementation.
• Q3 : Two ways how Development Teams can ensure a good application Architecture ?
  • A3 : Architecture is an ongoing discussion and the Development Teams should have a set of Architecture principles and follow them

More informations for the Scrum PSD certification here.

Updated : 03/09/2021