16 June 2021

The Scrum framework (6) : Scaled Scrum

Scaled Scrum :

  • Scaled Scrum is based on the Scrum framework and uses Scrum parts as its building blocks with some additions or changes within which multiple 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 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 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 releasable 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 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 or multiple Scrum Masters.

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.
    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
    Can have different Sprint lenghts
    Can have different Scrum Masters or the same Scrum Master
  • Q: How to start a big complex project?
    * A: Form 1-2 teams of best developers for implementing the core, add more teams later.
  • Q: A system is decomposed into elements like workflows, features, capabilities, etc. How it affects Scrum Teams on a scaled project?
    * A: It will be reflected in the implementation.

Scaled Scrum Architecture :

  • Q: Two ways how Dev Teams can ensure a good application architecture?
    * A : Architecture is an ongoing discussion
    * A : The DT should have a set of architecture principles and follow them

Scaled Scrum Definition of Done :

  • When multiple Development Teams are working on the same product they could (not should) have one Definition of Done 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 should not violate each other.

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. 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.
  • A Single Increment is needed at 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 Version control (main trunk) :

  • A company has multiple teams working on a single product with a single Product Backlog.
  • Each member of the teams frequently commit their code back to the main trunk, rather than each team managing their own branch.
  • Continuous Integration (to trunk) is a great state to aim for.
  • 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.

More informations for the Scrum PSD certification here.

Leave a Reply

Your email address will not be published. Required fields are marked *