MVP2MVP - Scaled Pro Scrum (The Nexus) · by Scrum.org – Improving the Profession of Software...

Post on 30-Jul-2020

4 views 0 download

Transcript of MVP2MVP - Scaled Pro Scrum (The Nexus) · by Scrum.org – Improving the Profession of Software...

4‐Nov‐15

1

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

by Scrum.org – Improving the Profession of Software Development

Scaled Professional Scrum

Richard HundhausenProfessional Scrum Developer

Professional Scrum Trainer

Co-creator of the Nexus

richard@accentient.com | @rhundhausen

#ScaledScrumIsStillScrum

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

ProductBacklog

One Scrum team doing work

4‐Nov‐15

2

3© 1993-2015 Scrum.org, All Rights Reserved

ProductBacklog

Three Scrum teams doing work

4© 1993-2015 Scrum.org, All Rights Reserved

ProductBacklog

Nine Scrum teams doing work

4‐Nov‐15

3

5© 1993-2015 Scrum.org, All Rights Reserved

What is Scaled Scrum

Number of Products

Number of Scrum Teams

1

1

>1

>1

Scrum

Painful

Scaled Scrum

Portfolio Management

6© 1993-2015 Scrum.org, All Rights Reserved

Organizations want to scale Scrum

Great results with small initiatives of one to three teams

Desire to gain similar benefits from larger initiatives

Looking for a straightforward approach that builds on their current knowledge and skills

4‐Nov‐15

4

7© 1993-2015 Scrum.org, All Rights Reserved

The Nexus Framework from Scrum.org

Refinement

8© 1993-2015 Scrum.org, All Rights Reserved

Nexus Roles, Events and Artifacts

Roles Events Artifacts

Development Teams The Sprint Product Backlog

Nexus Integration Team* Nexus Sprint Planning* Nexus Sprint Backlog*

Product Owner Sprint Planning Sprint Backlog

Scrum Master Nexus Daily Scrum* Integrated Increment

Daily Scrum

Nexus Sprint Review*

Sprint Retrospective

Nexus Sprint Retrospective*

Refinement

*Nexus specific

4‐Nov‐15

5

9© 1993-2015 Scrum.org, All Rights Reserved

The Nexus Integration Team

• The Nexus Integration Team is a Scrum Team.– Accountable for overall Nexus

• Members may be full or part time.– Membership in the Nexus

Integration Team takes precedence

• Composition may change between Sprints.

10© 1993-2015 Scrum.org, All Rights Reserved

The Nexus Framework from Scrum.org

Refinement

4‐Nov‐15

6

11© 1993-2015 Scrum.org, All Rights Reserved

The Nexus Framework from Scrum.org

Refinement

12© 1993-2015 Scrum.org, All Rights Reserved

The Nexus Framework from Scrum.org

Refinement

4‐Nov‐15

7

13© 1993-2015 Scrum.org, All Rights Reserved

The Nexus Framework from Scrum.org

Refinement

14© 1993-2015 Scrum.org, All Rights Reserved

The Nexus Framework from Scrum.org

Refinement

4‐Nov‐15

8

15© 1993-2015 Scrum.org, All Rights Reserved

The Nexus Framework from Scrum.org

Refinement

16© 1993-2015 Scrum.org, All Rights Reserved

Refinement

The Nexus Framework from Scrum.org

http://nexusguide.org

4‐Nov‐15

9

17© 1993-2015 Scrum.org, All Rights Reserved

Practices and tools to scale (Nexus workshop)

• 40 Practices– Story mapping

– Cross-team refinement

– Continuous integration

– Continuous build

– Sprint backlog as TDD

– …

• ALM tooling

18© 1993-2015 Scrum.org, All Rights Reserved

Managing the Nexus

Scaled Professional Scrum

“Put all your eggs in one basket and then watch that basket.”

– Mark Twain

4‐Nov‐15

10

19© 1993-2015 Scrum.org, All Rights Reserved

Descaling – integration is too difficult, too much overhead

• Reduce the overall pace by reducing the number of teams to a more sustainable number;

• Improve use of practices and tools; and,

• Clean up and integrate the current software so it can be built upon in future Sprints.

Productivity

Teams

20© 1993-2015 Scrum.org, All Rights Reserved

The Challenge of Large Scale Development

• We have found that the Nexus starts to fray and create confusion at around 9 teams.– We have experienced this across a range of companies and

industries.

• Dependencies and integration issues are magnified and can create chaos.

• The engineering environment and architecture are then employed to standardize work and remove dependencies.

• There is no guaranteed recipe at this scale – every project is unique.

4‐Nov‐15

11

21© 1993-2015 Scrum.org, All Rights Reserved

Nexus +

Nexuses One or more Nexuses for:• Product• Product functionality• Architecture• Infrastructure

Nexus+

22© 1993-2015 Scrum.org, All Rights Reserved

Nexus+

• Integrates multiple Nexuses;

• NIT+ has product and system architects;

• Events are scheduled immediately prior to Nexus events;

• Overall or linked Product Backlogs; and,

• No Nexus+ Sprint Backlog.

Nexus+

Nexuses

4‐Nov‐15

12

23© 1993-2015 Scrum.org, All Rights Reserved

Next Steps

• Scaling Workshops - http://bit.ly/1JJW9KF

• Nexus Guide - http://bit.ly/1i6zjHs

• Nexus Assessments - http://bit.ly/1M6olcg