Scrum kan vara svårt att använda i stor skala. Vi tittar på hur Kanban kan användas för att förstärka Scrum på företagsnivå genom att förbättra Scrum-of-Scrums, hjälpa produktägaren och stödja god beslutsfattandet på program eller avdelningsnivå. Talare är Christophe Achouiantz från Avega Group

1. Scaling Scrum
in the Enterprise
with Kanban
Christophe Achouiantz

2. First project with
Scrum: Success!
SM
Development
PO Team
Christophe Achouiantz

3. Let’s roll it out!
What could possibly
go wrong?
Project
or CIO
Manager
CM Architect
Team 1 Team 2 Team 3 Team n
Christophe Achouiantz

4. Dependencies!
Hand-overs
Code Project
Manager
API Specialists
CM Architect
Functions Timing
Team 1 Team 2 Team 3 Team n
Christophe Achouiantz Components

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

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

7. What we need
• Understand how the work Map value stream
flows (dependencies)
• Visualize the work, Visualize value
impediments, bottlenecks to stream
identify problems and risks
• Focus on what is top priority Limit WIP
Christophe Achouiantz

8. Enhance the
Scrum-of-Scrums
with Kanban
Christophe Achouiantz

9. 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. Define a process for the teams to follow
3. Visualize the organization and process
Christophe Achouiantz

10. Create an organization of Scrum
teams that map to the value stream
Dev.
Team
Dev.
Team
Idea PO
Team
Dev.
Team
Integration
Team Product
Dev.
Team
Dev.
Team
Christophe Achouiantz

11. Organization may need
to be complex
Dev.
Team
Integration
Team
Dev.
Team
Ideation PO Dev. Integration Production
Team Team Team Team Team
Dev. Integration
Team Team
Dev.
Team
Christophe Achouiantz

12. Visualize Organization
and Process
To Dev. & Inte- Pre-
Ideation Design Ready!
Do Test gration prod
Dev.
Team 1
Dev.
Team 2
Dev.
Team 3
Dev.
Team 4
Christophe Achouiantz

13. Identify Type of Work
Release 1.2 MMF 2322
Project A
As a pension saver, I
want to browse my
account history
Date Started
Ideation Integration
Design Pre-prod
Dev. Done!
Christophe Achouiantz

14. Visualize Type of Work
To Dev. & Inte- Pre-
Ideation Design Ready!
Do Test gration prod
Dev.
Team 1
Dev.
Team 2
Dev. Project A
Team 3
Release 1.1
Dev.
Team 4
Christophe Achouiantz
Support/Maintenance

15. Visualize Impediments
To Dev. & Inte- Pre-
Ideation Design Ready!
Do Test gration prod
Dev.
Team 1
Dev.
Team 2
Dev.
Team 3
Dev.
Team 4
Christophe Achouiantz

16. Visualization over time
• Can show variations over time
- release
- project Kanban board gives us
- MMF rich data that can be
- team used as leading indicator
- steps in the process
• WIP, Lead-times, cycle-times
(Cumulative Flow Diagrams)
• Impediments
Christophe Achouiantz

17. WIP and Lead-times over time
Cumulative Flow Diagram (CFD)
Can be done for each team,
release, project or MMF!
To Do
Lead-time
Design
Development & Test
PreProd
Integration Ready
Sprints under Release

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

19. Good decision-making
gives Control
Christophe Achouiantz

20. Control gives Scalability
Adding new teams becomes cheaper,
as coordination and synchronization is now cheaper
Christophe Achouiantz

21. Thank you!
Did you know?
Scrum can be used to scale Kanban...
Ask me!
christophe.achouiantz@avegagroup.se
Blog: http://blog.avegagroup.se/ChristopheAchouiantz
Twitter: ChrisAch
Christophe Achouiantz