scale scrum successfully with nexus - agile boston · • don’t scale flaccid scrum. scale...

1© 1993-2016 Scrum.org, All Rights Reserved

byScrum.org – Improving theProfession ofSoftwareDevelopment

Scaling Scrum with Nexus#scaledscrumisstillscrum

[email protected]

[email protected]

Amanwhocarriesacatbythetaillearnssomethinghecanlearninnootherway.

- MarkTwain


Improvingtheprofessionofsoftwaredevelopment


1,022,000+ AssessmentsTaken

8,700+ ProfessionalScrumProductOwners

2,700+ ProfessionalScrumDevelopers

63,000+ ProfessionalScrumMasters

The Home of Scrum

90% AgileTeamsUseScrum

160 ProfessionalScrumTrainers

Over51,000Taught

Americas,Europe,Africa,Oceania&Asia


1. Scale, the hype2. How far does Scrum go?3. How do you scale successfully?4. Nexus Framework, an introduction5. Scaled Professional Scrum with Nexus

Agenda

4


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..


• 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….


We are Focused on Scaling Product Delivery


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


One Scrum Team doing work

10© 1993-2016 Scrum.org, All Rights Reserved10

Nine Scrum Teams doing work


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


• 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.


Nexus Defined

Nexus –noun\ˈnek-səs\: a relationship or connection between people or things

Nexus is the exoskeleton of scaled Scrum- KenSchwaber


Nexus™


Scrum Framework


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


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 ProductBacklog


Nexus™


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


Nexus Integration Team Roles

A Nexus works off a single

Product Backlog

ProductOwnerAccountable formaximizingvalueoftheproduct, Product OwnerfortheNexus

ScrumMasterResponsibility forensuring theNexusframeworkisunderstood andenacted, oftenfacilitatestheNexuslevelevents

TeamMembersAccountable forsuccessfulintegration ofallworkbyallScrumTeams.TheseareoftenmembersofScrumTeamswithin theNexus


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


Nexus Integration Team – Modes of Working

• Coaching• Consulting• Highlighting dependencies• Identifying cross-team issues


Nexus™


Product Backlog Refinement Event

• Continuous elaboration• Conduct regular refinement

meetings• Run these as time-boxed events– Reduces big batches– Smoother transition across

releases– Time to consider the problem and

solution– Talk with SME’s outside the

Development Team– Allows dependencies to be

discovered earlier


Cross-Team Refinement

Sprintn

Sprintn +1

Sprintn +2 …

1

2

6

5 8

7

3

4TeamA

People

Technology

Domain

Software

External9

7

6

TeamB

TeamC


Nexus Sprint Planning

• Purpose– To coordinate and align all

Scrum Teams– To create plan(s) for the next

Sprint– To identify and manage in-

Sprint dependencies


Nexus Sprint Backlog

• Purpose– To provide visibility and

transparency into any and all dependencies that exist during the Sprint

• Potentially a mechanism to view all the Product Backlog items included in the Sprint


Nexus Daily Scrum

• Purpose–Make integration issues transparent

• The output of the Nexus Daily Scrum serves as input to each individual team’s Daily Scrum so they can plan their next day’s work


Nexus Sprint Review

• Purpose–Get feedback on the Integrated

Increment


Nexus Sprint Retrospective

• Purpose–Allows for shared challenges to be

addressed via bottom-up intelligence• Three parts:

1. Representatives from each Scrum Team meet to identify shared challenges

2. Scrum Team Retrospective3. Representatives from each Scrum

Team meet to discuss any actions needed for shared challenges


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


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


Scrum.org for next steps

Nexus Guide Assessment A Workshop


For Agile Boston

• Boston area workshop• July 13-14• Offering 25% discount to you all• Discount code 25OFFJULYSPS• Email [email protected] if you

have any problems


Scrum on!

Thank you.

[email protected]@pmoonk88@scrumdotorg

[email protected]@davidjwest @scrumdotorg


Scrum.org is a community. Connect.

Twitter@scrumdotorg

LinkedInLinkedIn.com

/company/Scrum.org

FacebookFacebook.com/Scrum.org

ForumsScrum.org/Community

RSSScrum.org/RSS

scale scrum successfully with nexus - agile boston · • don’t scale flaccid scrum. scale...

Documents