A Case of Nexus or Die Scaled Professional Scrum by Scrum.org Improving the Profession of Software Development Gunther Verheyen Shepherding Professional Scrum Scrum.org Agile+ market Den Bosch April 7, 2016
The Nexus. Craving Space for Collaboration. noun \ˈnek-səs\ : a relationship or connection between people or things http://www.merriam-webster.com/dictionary/nexus 2
A Software Development Program as is IT Program (4 teams, India) IT1 IT2 IT3 IT4 Codebas e Capability 1 Capability 2 Capability 3 Capability 4 Business Program Back-end team (11p) UX (design) team (10p) Widgets team (9p) Standards & guidelines team (9p) BE UX FE SG Configuration management Release management 3
Observations as is Focus = Capability 1 = Good Vision? Easiest! Fragile system Cross-team dependencies (Impediments?) Branched work No integrated Increments Long release stabilization time (syncing with 3-months releases) Separate backlogs, silo teams Autonomy? Business Priorities IT program? Respecting standards? 4
Back to basics: a system called Scrum Product Backlog Valuable Increment 5
Multiple Teams Building One Product 1. A product has one Product Backlog. 2. Multiple Teams create integrated Increments, that can wrap into releases. The Customer s Experience 6
Future Capabilities Capability 1 A Software Development Program Employing Nexus Product Backlog IT1 UX BE Nexus IT2 IT3 Valuable Increment FE IT4 Nexus Integration Team SG CM RM 7
The Program With Nexus Changes One Product Backlog Subset = Capability 1 Unit of delivery = Nexus Shared events Goal = integrated Increments Including IT program Nexus Integration Team Standards & Guidelines Configuration management Release management Challenges Integrated Increments? A dynamic, bottom-up re-invention of how the work is being done A fascinating discovery of Black Holes Adding external skills to the Nexus Integration Team Configuration Management Release Management Team changes within the Nexus (expected) 8
Nexus An Exoskeleton for 3-9 Scrum Teams 9
Prevent Dependencies to Corrupt Your Outcomes Anticipation* Overall Product Backlog Product Backlog Refinement Shared Sprint Planning Nexus Integration Team Reification** Frequent integration and testing Shared Daily Scrum Shared Sprint Review * The act of preparing for something. A prior action that takes into account or forestalls a later action. ** The process or result of reifying. Making something real, bringing something into being, or making something concrete. 10
Nexus enables: An improved Customer Experience Transparency (program, budget, progress, dependencies) An increased ability to adapt 11
Closing Empirical Management Explored 12
Scaled Scrum is still Scrum. 13
About Gunther Verheyen extreme Programming and Scrum since 2003 Professional Scrum Trainer Shepherding Professional Scrum at Scrum.org Co-developing the Scaled Professional Scrum framework at Scrum.org Author of Scrum A Pocket Guide (A Smart Travel Companion) and Scrum Wegwijzer (Een Kompas voor de Bewuste Reiziger) Mail gunther.verheyen@scrum.org Twitter @Ullizee Blog http://guntherverheyen.com 14
Look at Scrum.org for next steps The Nexus Guide The Open Assessment A Workshop 15
Scrum.org is a community. Connect. Forums Scrum.org /Community Twitter @scrumdotorg LinkedIn LinkedIn.com /company/scrum. org Facebook Facebook.com /Scrum.org RSS Scrum.org/RSS 16
T H A N K Y O U 17