scaling scrum in the enterprise with kanban
DESCRIPTION
We look at how Kanban can be used to enhance Scrum at the enterprise level. Enterprises often work with large or complex projects that require the cooperation of several Scrum teams. As synchonization between teams becomes crucial, we look at how Kanban can enhance the Scrum-of-Scrums to acheive control and sustainability.TRANSCRIPT
Christophe Achouiantz
Scaling Scrum in the Enterprise
with Kanban
Agile/Lean Coach
Agila Sverige, 2010-05-11
Christophe Achouiantz
First project with Scrum: Success!
DevelopmentTeamPO
SM
• 1 team• Best team• Low risk project
Christophe Achouiantz
Let’s roll-out Scrum in the Enterprise!
Team 1 Team 2 Team 3 Team n
CM Architect
Project Manager
What could possibly go wrong?
or CIO • Large project• Whole department
Christophe Achouiantz
Team 1
Dependencies!
Team 2 Team 3 Team n
CM Architect
Project Manager
Code
API
Components
Specialists
Hand-overs
Functions Timing
Christophe Achouiantz
Problems with several Scrum teams
• What’s our status? How are we doing?
• What is slowing us down (problems)?
• What will slow us down (risks)?
• What can I do as project manager / product owner / line manager to help?
Christophe Achouiantz
Solution: Scrum-of-Scrums?
• Hard to get it right
- Quickly degenerates in status report
• Focus on immediate issues
• Hard to understand the whole picture
Christophe Achouiantz
What we need
• Understand how the work flows (dependencies)
• Visualize the work, impediments, bottlenecks to identify problems and risks
• Focus on what is top priority
Map value stream
Limit WIP
Visualize value stream
Kanban?
Christophe Achouiantz
Enhance the Scrum-of-Scrums
with Kanban
Christophe Achouiantz
Scaling Scrum with Kanban
1. Create an organization of Scrum teams that map to the value stream (you might realize that you miss some teams)
2. In doing so, you define a process
3. Visualize the organization and process
Christophe Achouiantz
Dev.Team
Dev.Team
Dev.Team
Dev.Team
Dev.Team
IntegrationTeam
POTeam
Create an organization of Scrum teams that map to the value stream
Idea Product
Christophe Achouiantz
Dev.Team
Dev.Team
Dev.Team
Dev.Team
Dev.Team
IntegrationTeam
POTeam
IntegrationTeam
ProductionTeam
IdeationTeam
Organization may need to be complex
IntegrationTeam
POTeam
Christophe Achouiantz
IdeationTo Do
DesignDev. & Test
Inte-gration
Pre-prod
Ready!
Dev.Team 1
Dev.Team 2
Dev.Team 3
Dev.Team 4
Visualize Organization and Process
Christophe Achouiantz
IdeationTo Do
DesignDev. & Test
Inte-gration
Pre-prod
Ready!
Dev.Team 1
Dev.Team 2
Dev.Team 3
Dev.Team 4
Process
“Work”MMFs,feature,
functions, activities
Visualize Organization and Process
Organization(Teams)
Christophe Achouiantz
IdeationTo Do
DesignDev. & Test
Inte-gration
Pre-prod
Ready!
Dev.Team 1
Dev.Team 2
Dev.Team 3
Dev.Team 4
Visualize Organization and Process
Team’s responsibility(e.g. defects)
Team’s directactivities
Christophe Achouiantz
IdeationTo Do
DesignDev. & Test
Inte-gration
Pre-prod
Ready!
Dev.Team 1
Dev.Team 2
Dev.Team 3
Dev.Team 4
Identify Bottlenecks
Christophe Achouiantz
Project ARelease 1.2 MMF 2322
As a pension saver, I want to browse my
account history
Identify Type of Work
Date Started
Ideation Integration
Design Pre-prod
Dev. Done!
Christophe Achouiantz
IdeationTo Do
DesignDev. & Test
Inte-gration
Pre-prod
Ready!
Dev.Team 1
Dev.Team 2
Dev.Team 3
Dev.Team 4
Visualize Type of Work
Release 1.1Project A
Support/Maintenance
Christophe Achouiantz
IdeationTo Do
DesignDev. & Test
Inte-gration
Pre-prod
Ready!
Dev.Team 1
Dev.Team 2
Dev.Team 3
Dev.Team 4
Visualize Impediments
Christophe Achouiantz
IdeationTo Do
DesignDev. & Test
Inte-gration
Pre-prod
Ready!
Dev.Team 1
Dev.Team 2
Dev.Team 3
Dev.Team 4
Limit WIP to shorten Lead-times
4 5 3
Christophe Achouiantz
Visualization over time
• Can show variations over time
- release
- project
- MMF
- team
- steps in the process
• WIP, Lead-times, cycle-times(Cumulative Flow Diagrams)
• Impediments
Kanban board gives us rich data that can be
used as leading indicator
WIP and Lead-times over time
To Do
Design
Development & Test
IntegrationPreProd
Lead-time
Sprints under Release
Cumulative Flow Diagram (CFD)
Ready
Can be done for each:team, release, project or MMF!
Christophe Achouiantz
0
100
200
300
1 2 3 4
0
100
200
300
1 2 3 4
0
100
200
300
1 2 3 40
100
200
300
1 2 3 4
Whole IT Release 1.2
Projects in Release 1.2
0
100
200
300
1 2 3 4
Teams
0
100
200
300
1 2 3 40
100
200
300
1 2 3 4
WIP and Lead-times over timeCumulative Flow Diagram (CFD)
Christophe Achouiantz
Impediments over time
0
2
4
6
8
10
1 2 3 4 5 6 7 8 9 10
Impe
dim
ents
Weeks
Oops!Let’s do something
about it
Much better!Thanks for the help
Can be done for each:team, release, project or MMF!
Christophe Achouiantz
Using Kanban on top of Scrum gives good decision-making
• Gives a truthful, factual status
• Visible for anyone: anyone can help!
• Rich data gives leading indicators
- Identifies risks & problems ASAP
• Limit work in progress to what is prioritized
Christophe Achouiantz
Good decision-making gives Control
Christophe Achouiantz
Control gives Scalability
Adding new teams becomes cheaper, as coordination and synchronization is now cheaper
Christophe Achouiantz
Thank you!
Did you know?Scrum can be used to scale Kanban...
Ask me!
[email protected]: http://blog.avegagroup.se/ChristopheAchouiantzTwitter : ChrisAch