An introduction and overview of the Scrum @ Scale framework.

1. What’s it all about?
SATHPAL SINGH

2. A bit about me…quickly!
 Started as a Software Engineer over 20 years ago
– variety of hands-on engineering, management
leadership tech/digital roles across a variety of
sectors and industries
 Day Job – currently a Principal Engineer @ RBS
 Believe in the power of coaching & mentoring
 Passionate about visualisation & visual thinking

3. What will we be covering?
• COURSE FORMAT
• SCRUM
• WHY SCRUM@SCALE?
• FRAMEWORK OVERVIEW
• STRATEGY & DELIVERY
• ROLES & EVENTS
• EXECUTION & LEADERSHIP
• PATTERNS
• Q&A - CLOSING DISCUSSION

4. Course format
• REMOTE!
• SMALL DISTRIBUTED
COHORT
• 4 4HR SUNDAY EVENING
SESSIONS
• INTERACTIVE
• HOMEWORK…
• COACHING 

5. Scrum
“A framework within which people can
address complex adaptive problems while
productively and creatively delivering
viable products or services of the highest
possible value.”

7. Why
• LIGHTWEIGHT
• EASY TO UNDERSTAND
• USING SCRUM
TO SCALE SCRUM

8. Scaling - exponentially
• Leverage a scale-free architecture
• Common in biology
• Capability to evolve more
rapidly than other networks

9. Framework
overview

10. What & How

11. Roles
• PRODUCT OWNER
TEAM
• CHIEF PRODUCT
OWNER (CPO)
• SCRUM OF SCRUMS
MASTER (SoSM)

12. Product Owner Team
• A group of POs for each SoS
• Responsibilities:
• Create overarching vision
• Build prioritized backlog and avoid duplication
• Align teams’ priorities along a single enterprise backlog
• Create a DoD; resolve dependencies & co-ordinated release plan
• Determine metrics to monitor to gain insights on product

13. The CPO
• Responsibilities
• Co-ordinate priorities among POs
• Same as team PO role but at scale
• Set strategic version for SoS
• Single backlog for ALL the teams
• Work closely with their SoSM
• Monitor customer & SoS product feedback
• Leading the Meta Scrum event

14. Scrum of Scrums Master (SoSM)
• Responsibilities:
• Accountable for release of teams’ joint effort
• Visibility of progress & impediments backlog
• Remove impediments that the teams can’t
• Effectiveness of SoS;
• Work with POT to deploy a PI every Sprint

15. Events
• Scaled Daily Scrum (SDS)
• Meta Scrum

16. Scaled Daily Scrum (SDS)

17. Meta Scrum
• Meet once per sprint
• Focus:
• Organisation-level decision making
• CPO presents Backlog
• Stakeholders collaborate on
strategy, change, funding, resourcing & release
matters

18. Execution – how to implement
•Reference model
Executive Action Team (EAT)
Owns & executes the transformation strategy
EATs Impediments
Aligns the entire organisation

20. Leadership
• EXECUTIVE ACTION TEAM (EAT)
EXECUTIVE METASCRUM TEAM (EMT)

22. Pattern

23. Scrum Patterns
Stable Teams
Illegitimus Non-Interruptus
Whack-the-Mole
Swarming
Mitosis Value Stream Fork
Yesterday’s Weather

24. Patterns + Agile/Scrum
= Hyper-productivity

25. Round up…
• Only scale Scrum, if it’s great at team level
• Scrum @ Scale based on scale-free architecture
• Components focus on WHY, WHAT and HOW
• Scrum Patterns enable high performance
• Develop a reference model showing what
good looks like – drives scaling SUCCESS

26. References
• www.scrumatscale.com/ - Official site
• www.scrumplop.org/ - Pattern Community website
• sites.google.com/a/scrumplop.org/published-patterns/home – Published
patterns
• www.scrum.org/resources/scrum-guide – Scrum Guide
• www.scruminc.com/wp-
content/uploads/2014/05/teamsthatfinishearlyacceleratefaster.pdf -
Pattern paper
• https://scholarspace.manoa.hawaii.edu/bitstream/10125/60134/0694.pdf –
Process Efficiency paper (Jeff Sutherland, Frank Verbruggen et al.)

27. Book suggestions

28. www.linkedin.com/in/sathpal
@sathpal
visualsath
Questions?