scaling scrum: a case study on how the nexus helped ... · teams voted for their stars and...

ScalingScrum:AcasestudyonhowtheNexushelpedCapitalOneinacomplex,multi-teamdeliveryAWebcastbyValarmathyRangasamy andScrum.org

ModeratedbyEricNaiburg

ValarmathyRangasamy PatriciaKong

2© 1993-2017 Scrum.org, All Rights Reserved

1,700,000+ OpenAssessmentsTaken

130,000+ ProfessionalScrumCertifications

Scrum.orgisTheHomeofScrum

90% AgileTeamsUseScrum

193 ProfessionalScrumTrainers

TaughtPracticedeverywhere 86,000+

+12M UsingScrumDaily

ONEScrumGuide

©1993-2017Scrum.org,AllRightsReserved 3

• FreemonthlyWebinarbyScrum.org,withunifyingthemes:– Increasedfocusonempiricismandagility– Continuousdeliveryofbusinessvalue– BuildingtrustandrespectbetweenbusinessandI.T.

• Howyoucanplug-in…– RegisterandviewpreviouslyrecordedwebinarsatScrum.org/ScrumPulseorYoutube.com/scrumdotorg

– Tweetrequestsforfuturesessions,mention@scrumdotorg#scrumpulse

AboutScrumPulse


• Yourmicrophoneswillbemutedthroughout

• Weencouragequestionsanddiscussion!

– Tweetyourquestions:@scrumdotorg,#ScrumPulse

– Youcanalsotypeyourquestionsandcommentsintothewebinarquestionsbox:

QuickGuidelines


• Passionateservantleaderwithmorethan15yearsofITexperience

• Over10yearsofAgileconsultingexperience• ScrumMasterandAgileCoach• CertifiedinSPS(Scrum.org),PSMI(Scrum.org),CSM(ScrumAlliance),andSPC4.0(SAFe)

• Currentinterestisexploringvariousscalingapproaches

ValarmathyRangasamy


• ProductOwnerofEnterpriseSolutionsatScrum.org

• CurrentlyfocusedonEvidence-BasedManagement(measuringvalue)

• Co-authorof“ScalingScrumwithNexus”tobepublishedinDecember2017

• 13+yearsinproductmanagement,organizationalbehavior,ScrumandAgile

PatriciaKong


• DevelopanewproducttoGo-Livein3months• Coordinate5teamsworkingtowardbuildingoneproduct

– Pivot2existingScrumTeams– Onboard3newteamswithteammembersnewtothecompany

• Integrateanexternalinterface• Incorporatecuttingedgetechnologies- Angular4– UI,Node.Js –OL,Postgres(RDS)- Database,CloudInfrastructure,Microservices - API,KafkastreamsandSpringBatch

TheChallenge


EaseOfTraining It took less than an hour to introduce a team to

Nexus that was already familiar with Scrum!


SingleProductOwner

ProductOwner

Asst ProductOwner

ProductManagerSole decision

maker

Assisted the PO

Guided the PO

Product Management Team


SingleProductOwner- SingleProductBacklog

ProductOwnerNo more “Team level Product Backlogs!”


Investedcapacityforknowledgetransferonthenewplatformtoreduceconstraints

TeamComposition– MinimizeConstraints

Now any team can pull any work!

Flexibleteammembers

• AccountableforensuringthatanIntegratedIncrement(thecombinedworkcompletedbyaNexus)isproducedatleasteverySprint

• ConsistsofProductOwner,aScrumMaster,oneormoreNexusIntegrationTeamMembers

• ProvidedthenecessaryguidanceandsupportfortheScrumTeamsintheNexus

• ConsistedoftheProductOwner,aScrumMasterandTechSolutionOwner

• IncludedanysupportneededexternaltotheNexus

• HelpedplanforfutureSprintsandtrackedprogressandfocusedondependencies

NexusIntegrationTeam(NIT)

NexusGuide CapitalOne

The NIT helped our Nexus stay afloat and steering in the

right direction!


Refinement

Nexus Refinement minimized cross-team

dependencies and encouraged ownership

• Representativesfromeachteammettodiscussnextpriorities• PerformhighlevelRefinementtologicallysplitworkbetweenteams

• Storiesownedbyeachteamtentativelyidentified• POrefinedstorieswithrespectiveteams


Definitionof“Done”fortheNexus

Nexus DoD helped us have common alignment across

teams

• ApplicabletotheproductincrementdevelopedbytheNexusatleastbytheendoftheSprint

• Storyconsidered“Done”onlywhenitwasintegratedandtested• DoDsometimesnegotiatedwiththePOforaSprint


CombinedandCollaborativeSprintPlanning

Nexus Sprint Planning helped us ensure everyone was on the same

page!

• AllteamsmeteverySprinttoplaninacommonspace

• Eachteam’sSprintBacklogfinalized• OnedayforNexusSprintReview,NexusRetrospective,andNexusSprintPlanning


NexusDailyScrumandVisualManagement

Ready In-ProgressFEATURE

Feature1

Feature2

Sprint6 BacklogSprint5Sprint4 DoneSprint3Sprint2 Accepted

Feature3

CurrentSprint– Sprint3

Sprint1

ReleasePlan

NexusDailyScrumwasattendedbyrepresentativesfromeachteamandtheNIT


Nexus Sprint Review helped with knowledge sharing

and clarity!

• ReviewofintegratedproductwithNexusandexternalstakeholders

• Helpedeveryonestayonthesamepage

• AcombineddemonstrationofallfeaturesdevelopedinaSprint

NexusSprintReview– ACombinedProductReview


• TweakseverySprintbasedonfeedbackfromtheRetrospective(i.e.Refinement,automation,api)

• Actionitemswerefollowedupandupdatedprovidedinthesubsequentretrospective

• NexusrecommendsaNexuslevelretrofollowedbyteamlevelretros andthenagainaNexuslevelretro

NexusSprintRetrospective– ACombinedRetrospective

A combined retrospective as a

Nexus made common challenges

visible!


• StaroftheSprintAwards• SprinteroftheSprintAwards• Peerappreciationencouraged.Teamsvotedfortheirstarsandexplainedwhy

Celebrations This was a big energy booster and motivation

factor!


• Nexuscreatedfrequentopportunitiesforustoapplyagileconcepts.Ithelpedusinspectandadaptinaleanerandlighterway.

• Itisbestsuitedforsingleproductdevelopmentwith3+teams.• Nexushelpedusreleaseourproduct3weeksAHEAD ofschedule.• Ithelpedourteamscometogetherandkeepthemmotivatedasoneunit.

• WhenourNexuswasaskedfor1wordabouttheprogram,TEAMWORK stoodoutandIcouldn’tagreemore!

SummaryandWhatWeLearnedEase of

getting started and teamwork!


• Weencouragequestionsanddiscussion!– Youcanalsotypeyourquestionsandcommentsintothewebinarquestionsbox:

– Tweetyourquestions:@scrumdotorg,#ScrumPulse

WelcometoOurPanelDiscussion

Morequestions?TapintothecollectiveexperienceandexpertiseoftheScrum.orgcommunity.

Scrum.org/forum

ArticlesbyourProfessionalScrumExpertstofurtheryourScrumknowledgeandimproveyourAgilepractices.

Scrum.org/blog

ConnectwiththeScrum.orgCommunity

Scrum.org Forum Scrum.org Blog


ThankYou!Scrum.org/ScrumPulse | @scrumdotorg


NexusDailyScrumandVisualManagementcontd.

Vote

Team1

TeamTeam1

Team2

Team3

Team4

Issues• Issue1– Targetdate– Owner• Issue2– Targetdate– Owner

Risks• Risk1– Owner• Risk2– Owner

ImportantmilestonesReleasePilot– DateReleasetoonsiteagents- Date

Teamconfidencevoting

6,7,6,9

5,6,4,8

10.8.7,9

4,6,7,8


NexusDailyScrumandVisualManagementcontd.

scaling scrum: a case study on how the nexus helped ... · teams voted for their stars and...

Documents