The slides from the Nexus workshop run at the South Wales Agile Group 22 Nov 2018

1. v 4.2d © 1993 – 2017 Scrum.org All Rights Reserved
Scaling Scrum with Nexus
#ScaledScrumisStillScrum
@ScrumDotOrgSimon Reindl | Cardiff | 22 Nov 2018 1

2. v 4.2d © 1993 – 2017 Scrum.org All Rights Reserved 2
Improving the Profession of
Software Delivery

3. v 4.2d © 1993 – 2017 Scrum.org All Rights Reserved
The purpose of
“scaling is to get
more done in a
given timeframe.
But what do you
want more...
Output or Value?
Why Scale?
3
• Because we need to go faster?
• Because we have a lot of people?
• Why else?

4. v 4.2d © 1993 – 2017 Scrum.org All Rights Reserved
MIN
14Sprint 1
We are building a zoo catalogue!

5. v 4.2d © 1993 – 2017 Scrum.org All Rights Reserved
MIN
14Sprint 2
We are building a zoo catalogue!

6. v 4.2d © 1993 – 2017 Scrum.org All Rights Reserved
The Scrum Framework

7. v 4.2d © 1993 – 2017 Scrum.org All Rights Reserved
Nexus™

8. v 4.2d © 1993 – 2017 Scrum.org All Rights Reserved
The rule of one
Product
Product Owner
Product Backlog
Increment
Branch

9. v 4.2d © 1993 – 2017 Scrum.org All Rights Reserved
Nexus™

10. v 4.2d © 1993 – 2017 Scrum.org All Rights Reserved
• Identify and resolve or minimize
dependencies:
• Ongoing & persistent
• In all dimensions
• Prior to work occurring
• Reactive to ensure that
undetected dependencies
aren’t corrupting outcomes:
• Frequent integration
• Acceptance testing
• Continual build and delivery
• Minimize technical debt
Essence of Scaling
ANTICIPATION* REIFICATION**
** The process or result of reifying.
Making something real, bringing something into
being, or making something concrete.
* The act of preparing for something.
A prior action that takes into account or forestalls a
later action.

11. v 4.2d © 1993 – 2017 Scrum.org All Rights Reserved
TAKE
AWAY
Nail it before you
scale it

12. v 4.2d © 1993 – 2017 Scrum.org All Rights Reserved
• Scale for value not for output.
• Nexus extends Scrum by creating a network among the teams.
• Be rigorous about removing dependencies and creating an
Integrated Increment at least every Sprint.
• Integration is also about the connection between people.
• Scrum provides a great framework from which to scale with Nexus.
• And remember, without first implementing the foundational Scrum
concepts, any scaling will be painful and will actually reduce
productivity.
Summary

13. v 4.2d © 1993 – 2017 Scrum.org All Rights Reserved
• Stabilization
• Dependencies
• Alignment
• Scrum experience
• Teams identified / Nexus
overview
• Nexus Integration Team
identified
• Single Product Backlog
• Definition of Done
• Sprint cadence identified
Getting Started with Nexus Framework
Common Challenges Pre-requisites

14. v 4.2d © 1993 – 2017 Scrum.org All Rights Reserved
Nexus Resources
Nexus Guide
Assessment
AssessmentsWorkshops

15. v 4.2d © 1993 – 2017 Scrum.org All Rights Reserved
Professional Scrum at Scrum.org
22
www.scrum.org/courses
Everyone! Scrum Masters・Managers・
Scrum Team Members
Experienced Scrum Masters Product Owners・Product Managers・
Advanced Practitioners
All members of a Scrum Team including:
Developers・Scrum Masters・Product
Owners・Analysts・Testers …
Development Leads and Managers・
Scrum Masters・Project Managers・
Advanced Practitioners
Managers・Leaders・Product Owners・
Scrum Masters
All members of a Scrum Team including:
Development Team Members・Scrum
Masters・Product Owners

16. v 4.2d © 1993 – 2017 Scrum.org All Rights Reserved23
Thank You!
KEEP
CALM
AND
SCRUM
ON