1 © 1993-2016 Scrum.org, All Rights Reserved
byScrum.org–ImprovingtheProfessionofSo8wareDevelopment
Scaling Scrum with Nexus #scaledscrumisstillscrum
Amanwhocarriesacatbythetaillearnssomethinghecanlearninnootherway.
-MarkTwain
2 © 1993-2016 Scrum.org, All Rights Reserved
Who am I ?
• Product Owner (CEO) Scrum.org
• Former – CPO Tasktop – VP RD Forrester Research – Product Mgr RUP
• [email protected] • @DavidJWest • LinkedIn DavidJustinWest
3 © 1993-2016 Scrum.org, All Rights Reserved
Improvingtheprofessionofso0waredevelopment
4 © 1993-2016 Scrum.org, All Rights Reserved
1,146,000+OpenAssessmentsTaken
95,000+ProfessionalScrumCerAficaAons
The Home of Scrum
90%AgileTeamsUseScrum
167ProfessionalScrumTrainers
TaughtPracAcedeverywhere 60,000+
+12MUsingScrumDaily
ONEScrumGuide
5 © 1993-2016 Scrum.org, All Rights Reserved
1. Scale, the hype 2. How far does Scrum go? 3. How do you scale successfully? 4. Nexus Framework, an introduction 5. Scaled Professional Scrum with Nexus
Agenda
5
6 © 1993-2016 Scrum.org, All Rights Reserved
When Organizations Talk about Scale they mean…
• More people delivering working software with an Agile approach (scaling product delivery) – More teams and different project types
• Agile growing outside of delivery to include other supporting functions (fixing water-scrum-fall) – Adding Portfolio Planning, EA, Support, etc..
7 © 1993-2016 Scrum.org, All Rights Reserved
• You have an organization in place that allows product teams to deliver products
• That the high level or portfolio planning has been done elsewhere
• That the funding, staffing and support functions of those product teams is being managed
We Assume….
8 © 1993-2016 Scrum.org, All Rights Reserved
We are Focused on Scaling Product Delivery
9 © 1993-2016 Scrum.org, All Rights Reserved
Scrum is a Key Part of ANY Scaling Strategy
• Building on the success of Scrum at the team level
• Adopting methodologies such as SAFe, LeSS
10 © 1993-2016 Scrum.org, All Rights Reserved
One Scrum Team doing work
11 © 1993-2016 Scrum.org, All Rights Reserved 11
Nine Scrum Teams doing work
12 © 1993-2016 Scrum.org, All Rights Reserved
When scaling, several challenges emerge: • Ensuring a shared goal is understood and aimed for • Coordinating work across many teams • Allowing for self-organization while still achieving consistency • Releasing a fully integrated and tested Increment of software
as often as possible • Identifying dependencies between teams, between
components of the software, and between requirements • Removing or minimizing those dependencies
Challenges in scaled development
13 © 1993-2016 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 Product Delivery
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.
14 © 1993-2016 Scrum.org, All Rights Reserved
Nexus Defined
Nexus –noun \ˈnek-səs\ : a relationship or connection between people or things
Nexus is the exoskeleton of scaled Scrum
-KenSchwaber
15 © 1993-2016 Scrum.org, All Rights Reserved 15
16 © 1993-2016 Scrum.org, All Rights Reserved
Nexus™
17 © 1993-2016 Scrum.org, All Rights Reserved
Scrum Framework
18 © 1993-2016 Scrum.org, All Rights Reserved 18
Nexus Roles, Events, and Artifacts
ROLES EVENTS ARTIFACTS
DEVELOPMENTTEAMS
PRODUCTOWNER
NEXUSINTEGRATIONTEAM
SCRUMMASTER
THESPRINT
SPRINTPLANNING
NEXUSSPRINTPLANNING
NEXUSDAILYSCRUM
DAILYSCRUM
NEXUSSPRINTREVIEW
SPRINTRETROSPECTIVE
NEXUSSPRINTRETROSPECTIVE
REFINEMENT
PRODUCTBACKLOG
SPRINTBACKLOG
NEXUSSPRINTBACKLOG
INTEGRATEDINCREMENT
NEXUSGOAL
19 © 1993-2016 Scrum.org, All Rights Reserved 19
Nexus Roles, Events, and Artifacts
ROLES EVENTS ARTIFACTS
DEVELOPMENTTEAMS
PRODUCTOWNER
NEXUSINTEGRATIONTEAM
SCRUMMASTER
THESPRINT
SPRINTPLANNING
NEXUSSPRINTPLANNING
NEXUSDAILYSCRUM
DAILYSCRUM
NEXUSSPRINTREVIEW
SPRINTRETROSPECTIVE
NEXUSSPRINTRETROSPECTIVE
REFINEMENT
PRODUCTBACKLOG
SPRINTBACKLOG
NEXUSSPRINTBACKLOG
INTEGRATEDINCREMENT
NEXUSGOAL
20 © 1993-2016 Scrum.org, All Rights Reserved
Scaled Scrum is Still Scrum
• Nexus introduces new roles, events, and artifacts
• The Product Backlog is still the Product Backlog – The Product Backlog may have several levels
of decomposition – Dependencies between Product Backlog items
should be minimized
1 Product =
1 Product Backlog
21 © 1993-2016 Scrum.org, All Rights Reserved
Nexus™
22 © 1993-2016 Scrum.org, All Rights Reserved
The Nexus Integration Team (NIT)
• Purpose – Provide transparent
accountability for Nexus integration
• Accountability – Ensure that an integrated
increment is produced at least every Nexus Sprint
23 © 1993-2016 Scrum.org, All Rights Reserved
Nexus Integration Team Roles
A Nexus works off a single
Product Backlog
ProductOwnerAccountableformaximizingvalueoftheproduct,ProductOwnerfortheNexus
ScrumMasterResponsibilityforensuringtheNexusframeworkisunderstoodandenacted,o\enfacilitatestheNexuslevelevents
TeamMembersAccountableforsuccessfulintegraAonofallworkbyallScrumTeams.Theseareo\enmembersofScrumTeamswithintheNexus
24 © 1993-2016 Scrum.org, All Rights Reserved
The Purpose of the Nexus Integration Team
• The Scrum Teams do the integration work; however, the Nexus Integration Team remains accountable
• Activities – Helps coordinate work between the teams – Raises awareness of dependencies as early as possible – Ensures integration tools and practices are known and used – Serves as consultants, coaches, and communication links – Sometimes they will even assist with the work – Facilitates shared architecture/infrastructure – Raises transparency
25 © 1993-2016 Scrum.org, All Rights Reserved
Nexus Integration Team – Modes of Working
• Coaching • Consulting • Highlighting dependencies • Identifying cross-team
issues
26 © 1993-2016 Scrum.org, All Rights Reserved
Nexus™
27 © 1993-2016 Scrum.org, All Rights Reserved
You can scale as long as you continuously…
• Identify and remove dependencies; • Integrate work across all level; • Create and inspect integrated increments
regularly; • Provide adequate tooling and skills; and, • Inspect and adapt frequently.
Continuous integration,
build, test and delivery test adequacy of
effort
28 © 1993-2016 Scrum.org, All Rights Reserved
Ending
• Don’t scale flaccid Scrum. Scale Professional Scrum. • Nexus creates connections between Scrum Teams and is the
exoskeleton of scaled Scrum. • At scale, Refinement is not optional. • Bottom-up intelligence. Solutions need to come from the
teams, not from “above.” • To scale, be rigorous about removing dependencies and
creating an Integrated Increment every Sprint. • #scaledscrumisstillscrum
29 © 1993-2016 Scrum.org, All Rights Reserved
30 © 1993-2016 Scrum.org, All Rights Reserved
But ’Bad’ Scrum will mean VERY ’Bad’ Scaled Scrum
• Lack of clear Product Ownership
• Inability to realign to products • Large amount of technical
debt • Heavy dependency on legacy
systems that are a Spider’s web of dependencies
• Lack of consistency • Complex, imposed
organizational models
• Lack of good engineering skills
• People being on multiple projects / products
• No training, ,mentoring and coaching budget
• Complex partner relationships with no shared objectives
31 © 1993-2016 Scrum.org, All Rights Reserved
32 © 1993-2016 Scrum.org, All Rights Reserved
Scrum.org for next steps
Nexus Guide Assessment A Workshop
33 © 1993-2016 Scrum.org, All Rights Reserved 33
34 © 1993-2016 Scrum.org, All Rights Reserved
35 © 1993-2016 Scrum.org, All Rights Reserved
Scrum on!
Thank you.
[email protected] @davidjwest@scrumdotorg
36 © 1993-2016 Scrum.org, All Rights Reserved
Scrum.org is a community. Connect.
Twi3er@scrumdotorg
LinkedInLinkedIn.com/company/Scrum.org
FacebookFacebook.com/Scrum.org
ForumsScrum.org/Community
RSSScrum.org/RSS
37 © 1993-2016 Scrum.org, All Rights Reserved 37 © 1993-2015 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
38 © 1993-2016 Scrum.org, All Rights Reserved
When we say “scaling”
• We are NOT referring to organizational transformation, becoming “agile”.
• We are NOT referring to spreading Scrum throughout a development and/or product management organization.
• We ARE providing a framework for efficiently employing many people and Scrum teams on a project, program, or initiative.
39 © 1993-2016 Scrum.org, All Rights Reserved 39
Scaling…
Water Agile Fall