Scaling Scrum with Nexus #scaledscrumisstillscrum

Transcription

1 Scaling Scrum with Nexus #scaledscrumisstillscrum by Scrum.org Improving the Profession of Software Development DAVE CEO Scrum.org PATRICIA Product Owner Scaling Scrum.org A man who carries a cat by the tail learns something he can learn in no other way. - Mark Twain 1

2 Improving the profession of software development 2

3 The Home of Scrum 90% Agile Teams Use Scrum 1,022,000+ Assessments Taken 160 Professional Scrum Trainers 63,000+ Professional Scrum Masters Over 51,000 Taught 8,700+ Professional Scrum Product Owners Americas, Europe, Africa, Oceania & Asia 2,700+ Professional Scrum Developers 3

4 Agenda 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 4 4

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

6 We Assume. 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 6

7 We are Focused on Scaling Product Delivery 7

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

9 One Scrum Team doing work 9

10 Nine Scrum Teams doing work 1 10

11 Challenges in scaled development 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 11

12 Essence of Scaling Product Delivery Anticipation* Identify and resolve or minimize dependencies: Ongoing & persistent In all dimensions Prior to work occurring * The act of preparing for something. A prior action that takes into account or forestalls a later action. Reification** Reactive to ensure that undetected dependencies aren t corrupting outcomes: Frequent integration Acceptance testing Continual build and delivery Minimize technical debt ** The process or result of reifying. Making something real, bringing something into being, or making something concrete. 12

13 Nexus Defined Nexus noun \ˈnek-səs\ : a relationship or connection between people or things Nexus is the exoskeleton of scaled Scrum - Ken Schwaber 13

14 1 14

15 Nexus 15

16 Scrum Framework 16

17 Nexus Roles, Events, and Artifacts ROLES EVENTS ARTIFACTS DEVELOPMENT TEAMS NEXUS INTEGRATION TEAM PRODUCT OWNER SCRUM MASTER THE SPRINT NEXUS SPRINT PLANNING SPRINT PLANNING NEXUS DAILY SCRUM DAILY SCRUM NEXUS SPRINT REVIEW NEXUS SPRINT RETROSPECTIVE PRODUCT BACKLOG NEXUS SPRINT BACKLOG SPRINT BACKLOG INTEGRATED INCREMENT NEXUS GOAL SPRINT RETROSPECTIVE REFINEMENT 1 17

18 Nexus Roles, Events, and Artifacts ROLES EVENTS ARTIFACTS DEVELOPMENT TEAMS NEXUS INTEGRATION TEAM PRODUCT OWNER SCRUM MASTER THE SPRINT NEXUS SPRINT PLANNING SPRINT PLANNING NEXUS DAILY SCRUM DAILY SCRUM NEXUS SPRINT REVIEW NEXUS SPRINT RETROSPECTIVE PRODUCT BACKLOG NEXUS SPRINT BACKLOG SPRINT BACKLOG INTEGRATED INCREMENT NEXUS GOAL SPRINT RETROSPECTIVE REFINEMENT 1 18

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

20 Nexus 20

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

22 Nexus Integration Team Roles Product Owner Accountable for maximizing value of the product, Product Owner for the Nexus Scrum Master Responsibility for ensuring the Nexus framework is understood and enacted, often facilitates the Nexus level events A Nexus works off a single Product Backlog Team Members Accountable for successful integration of all work by all Scrum Teams. These are often members of Scrum Teams within the Nexus 22

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

24 Nexus Integration Team Modes of Working Coaching Consulting Highlighting dependencies Identifying cross-team issues 24

25 Nexus 25

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

27 Cross-Team Refinement Sprint n Sprint n + 1 Sprint n +2 People Team A Technology Domain Team B Software Team C External 27

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

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

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

31 Nexus Sprint Review Purpose Get feedback on the Integrated Increment 31

32 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 Retrospective 3. Representatives from each Scrum Team meet to discuss any actions needed for shared challenges 32

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

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

35 Scrum.org for next steps Nexus Guide Assessment A Workshop 35

36 For Agile Boston Boston area workshop July Offering 25% discount to you all Discount code 25OFFJULYSPS if you have any problems 36

37 37

38 Scrum on! Thank @scrumdotorg 38

39 Scrum.orgis a community. Connect. Forums Scrum.org /Community LinkedIn LinkedIn.com /company/scrum.or g Facebook Facebook.com /Scrum.org RSS Scrum.org/RSS 39