This document provides an overview of the Nexus framework for scaling Scrum to multiple teams. Nexus introduces an integration team that is responsible for integrating the work of individual Scrum teams and ensuring the definition of done is met at each sprint's integrated increment. It also includes layered ceremonies that coordinate work across teams such as Nexus sprint planning and reviews. The key principles of Scrum like transparency, inspection, and adaptation still apply at scale with Nexus, allowing Scrum to scale fractally through these coordinated practices across multiple teams.

1. Nexus – Scaled
Professional Scrum
An Overview
India Agile Tour
2015 Chennai
Oct.
28
S R V Subrahmaniam
PMP, ACP, CSP
SAFe Program Consultant
(SPC)
Altimetrik

2. Slide 2
When Scaling, the context is different
CONTEXT
Single team Agile at Scale
7-9 > 100sTeam Size
Co-located GlobalGographic Distribution
Single Division Multi-departmentOrganizational Distribution
Less or none Life CriticalCompliance
Straightforward ComplexDomain Complexity
Straightforward Multi-platform / complexTechnical Complexity
Less or none Upstream / DownstreamIntegration needs
Homogenous Heterogenous mixEnvironment complexity

3. Slide 3
Case with multiple
teams
CONTEXT
▸ Can velocity scale
linearly? i.e. to achieve
more velocity can we add
more teams?
▸ Dependencies will
dampen the velocity
Slide adapted from Nexus presentation in Scrum.org
▸ Ken Schwaber calling it as
Reification – making a
concrete, worthwhile
integrated product
consumes additional
overhead
▸ Continuous Integration
▸ Automation

4. Slide 4
The Nexus™
Framework
NEXUS
Image source: https: / / www.s c rum . org/ portal s /0/ pres ent ati ons /Ken% 20S chwaber%20 -%20Sc aled% 20P rof es sional%20Sc rum .pdf
One new team and four extended ceremonies for for 3- 9 Scrum Teams

5. Slide 5
Integration Team
NEXUS
▸ A scrum team responsible
for producing the
integrated increment.
▸ Owner of ‘Definition of
Done’ applied at
Integrated Increment
during the Sprint.
Slide adapted from Scaled Agile Framework public slidedeck
▸ Nexus team members can
be part-time, i.e. can be
part of individual scrum
teams, but their
Integration team
membership takes priority

6. Slide 6
Layered Nexus Ceremonies
NEXUS
Sprint Planning
Nexus Sprint Goal
formulated jointly.
Teams plan their own
individual backlogs
Align for dependancies
Review
A single demo of the
integrated product
Daily Stand-up
Nexus daily scrum
precedes daily stand-up to
discuss product integration,
dependencies and
information sharing needs
Retrospective
Identify shared issues
Perform individual team
retros
Align on actions

7. Slide 7
Nexus Work Products
NEXUS
Nexus Sprint Goal
Nexus Sprint Goal
formulated jointly.
Nexus Sprint Backlog
Highlights the
dependancies
Product Backlog
Single backlog for the
Nexus team well groomed
with dependancies noted
Integrated Work
Product
Frequently integrated

8. Slide 8
So Scrum is indeed fractal at Scale!
With principles of Scrum intact
Principles Scale fractally
Underlying Principles of Transperancy,
Visibility, Frequent Inspection and
Adaptation, Continous Improvement apply
Practices do, in Nexus
Layered Sprint ceremonies help it
achieve
Pythogoras Tree
CLOSURE
A fractal is a natural phenomena and a
mathematical set. What they have in common is a
repeating pattern that displays at every scale.
“discovery and emergence through the empirical process”
Gunther Verheyen

9. QUESTIONS &
ANSWERS
Go ahead. Don‘t hesitate.

10. Slide 10
Let us stay in touch!
CONTACT
Twitter
twitter.com/srv_subbu
LinkedIn
ln.linkedin.com/in/srvsubbu
E-Mail
Srv.subbu@yahoo.in

11. THANK
YOU
For your attention!