Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
© 1993-2017 Scrum.org, All Rights Reserved
Scrum & Kanban – BetterTogether?
Some Scrum/Kanban Myths &
What Professional Sc...
© 1993-2017 Scrum.org, All Rights Reserved 2
© 1993-2017 Scrum.org, All Rights Reserved 3
We’re privileged – We can mix colors!
© 1993-2017 Scrum.org, All Rights Reserved
Survey
4
© 1993-2017 Scrum.org, All Rights Reserved
Scrum
5
• Strength: Optimized for value
delivery; well defined
• Weakness: mini...
© 1993-2017 Scrum.org, All Rights Reserved
Kanban
6
• Strength: Optimized for flow
• Weakness: No rules; deferred
value de...
© 1993-2017 Scrum.org, All Rights Reserved
It’s about being Professional
7
Scrum
Professional
© 1993-2017 Scrum.org, All Rights Reserved 8
So what is Professional Scrum?
© 1993-2017 Scrum.org, All Rights Reserved 9
© 1993-2017 Scrum.org, All Rights Reserved 10
So Why Kanban?
We set out to help practitioners figure out
how to do *Profes...
© 1993-2017 Scrum.org, All Rights Reserved
Kanban Core Practices –This is what *Professional* Kanban looks like…
1. Visual...
© 1993-2017 Scrum.org, All Rights Reserved
1.Visualize + 2. Limit Work in Progress
• work items
• workflow
• howWork In
Pr...
© 1993-2017 Scrum.org, All Rights Reserved
3. Actively Manage Items in Progress - Required Metrics
• To actively manage wo...
© 1993-2017 Scrum.org, All Rights Reserved
4. Make Policies Explicit
Explicit policies ensure process transparency and ena...
© 1993-2017 Scrum.org, All Rights Reserved
5. Improve Collaboratively
15
© 1993-2017 Scrum.org, All Rights Reserved 16
Myth /Truth?
Where are the PEOPLE in Kanban?
© 1993-2017 Scrum.org, All Rights Reserved 17
kanban doesn't encourage creating effective teams
© 1993-2017 Scrum.org, All Rights Reserved 18
kanban is all about manufacturing, software isn't manufacturing
© 1993-2017 Scrum.org, All Rights Reserved 19
Isn’t Scrum just Kanban with a bigger batch size?
© 1993-2017 Scrum.org, All Rights Reserved 20
Scrum is for … Kanban is for …
kanban is all about manufacturing, software i...
© 1993-2017 Scrum.org, All Rights Reserved 21
Our Scrum team has evolved to become a Kanban team.
© 1993-2017 Scrum.org, All Rights Reserved 22
We do Kanban because we can't plan out for an entire Sprint.
© 1993-2017 Scrum.org, All Rights Reserved 23
Scrum is revolutionary; Kanban is evolutionary.
Kanban always starts with wh...
© 1993-2017 Scrum.org, All Rights Reserved 24
kanban always starts with what you got
© 1993-2017 Scrum.org, All Rights Reserved 25
Kanban accepts and reinforces command and control / waterfall mindset
© 1993-2017 Scrum.org, All Rights Reserved 26
Where are the PEOPLE in Kanban?
© 1993-2017 Scrum.org, All Rights Reserved 27
Myth /Truth?
Where are the PEOPLE in Kanban?
© 1993-2017 Scrum.org, All Rights Reserved
Changes you can try in your Scrum teams
28
© 1993-2017 Scrum.org, All Rights Reserved
Use a Kanban Board as your Sprint Backlog
29
© 1993-2017 Scrum.org, All Rights Reserved
Make more of your processTransparent by making more policies explicit
30
THE De...
© 1993-2017 Scrum.org, All Rights Reserved
Work Item Age / Fighting Zombies
31
© 1993-2017 Scrum.org, All Rights Reserved
The Banana PeelTechnique
32
© 1993-2017 Scrum.org, All Rights Reserved
Flow-based Sprint Planning
• Leverage the Sprint Goal
• You don’t need to plan ...
© 1993-2017 Scrum.org, All Rights Reserved
Flow-based Sprint Planning
• Work planned for the first days of the Sprint by t...
© 1993-2017 Scrum.org, All Rights Reserved
Flow-based Sprint Planning
35
© 1993-2017 Scrum.org, All Rights Reserved
Flow-based Daily Scrums
36
• Flow/Pull/Hebrew-mode –Work the Kanban board right...
© 1993-2017 Scrum.org, All Rights Reserved
Flow-based Sprint Reviews
• What is our current throughput?
• How does this imp...
© 1993-2017 Scrum.org, All Rights Reserved
Flow-based Retrospectives
Stop
Start
MoreLess
Keep
• Is our cycle time decreasi...
© 1993-2017 Scrum.org, All Rights Reserved
Helping more Scrum teams be Professional using Kanban,
Helping Kanban teams be ...
© 1993-2017 Scrum.org, All Rights Reserved
Thank
You
40
© 1993-2017 Scrum.org, All Rights Reserved
Connect with the Scrum.org & AgileSparks community
Twitter
@scrumdotorg
LinkedI...
Upcoming SlideShare
Loading in …5
×

Scrum and Kanban Sitting In A Tree...

739 views

Published on

Scrum & Kanban - Better Together? Talk delivered at Agile Boston w/ Dave West of Scrum.org in October 2018
It's time to call an end to this stupid civil war within the agile camp. The best agile teams already know that it is not a choice between Scrum and Kanban, but they are complementary. Scrum teams improve when they start to look at flow inside and outside their sprints. Kanban teams improve when they have a disciplined cadence, and effective Product Ownership and Scrum Mastership.

In this session, we will look at:

Common Ground - The foundations that both approaches highlight
Complementary Practices - what can we add from Kanban to our Scrum and vice versa
Key differences - where you really need to make a choice
Myths - differences that are talked about which really are not there

Published in: Business

Scrum and Kanban Sitting In A Tree...

  1. 1. © 1993-2017 Scrum.org, All Rights Reserved Scrum & Kanban – BetterTogether? Some Scrum/Kanban Myths & What Professional Scrum+Kanban can look like… Dave West Product Owner & CEO Scrum.org Dave.West@scrum.org @DavidJWest YuvalYeret Enterprise Lean/Agile Consultant/Trainer AgileSparks Yuval@AgileSparks.com @YuvalYeret
  2. 2. © 1993-2017 Scrum.org, All Rights Reserved 2
  3. 3. © 1993-2017 Scrum.org, All Rights Reserved 3 We’re privileged – We can mix colors!
  4. 4. © 1993-2017 Scrum.org, All Rights Reserved Survey 4
  5. 5. © 1993-2017 Scrum.org, All Rights Reserved Scrum 5 • Strength: Optimized for value delivery; well defined • Weakness: mini-waterfall
  6. 6. © 1993-2017 Scrum.org, All Rights Reserved Kanban 6 • Strength: Optimized for flow • Weakness: No rules; deferred value delivery
  7. 7. © 1993-2017 Scrum.org, All Rights Reserved It’s about being Professional 7 Scrum Professional
  8. 8. © 1993-2017 Scrum.org, All Rights Reserved 8 So what is Professional Scrum?
  9. 9. © 1993-2017 Scrum.org, All Rights Reserved 9
  10. 10. © 1993-2017 Scrum.org, All Rights Reserved 10 So Why Kanban? We set out to help practitioners figure out how to do *Professional* Kanban within a *Professional* Scrum context
  11. 11. © 1993-2017 Scrum.org, All Rights Reserved Kanban Core Practices –This is what *Professional* Kanban looks like… 1. Visualize 2. LimitWork-in-Progress 3. Actively Manage Items in Progress 4. Make Policies Explicit 5. Improve Collaboratively 11
  12. 12. © 1993-2017 Scrum.org, All Rights Reserved 1.Visualize + 2. Limit Work in Progress • work items • workflow • howWork In Progress is limited • Visualization of a Service Level Expectation (SLE) • Visualization of process policies 12
  13. 13. © 1993-2017 Scrum.org, All Rights Reserved 3. Actively Manage Items in Progress - Required Metrics • To actively manage work in progress you must track when work begins and when work begins and when work is done. • CycleTime:The elapsed time between when works starts and when work finishes. • Work item age:The time between when works starts and the current time. • Throughput:The total number of items of items finished per unit of time. 13
  14. 14. © 1993-2017 Scrum.org, All Rights Reserved 4. Make Policies Explicit Explicit policies ensure process transparency and enable inspection and adaptation 14
  15. 15. © 1993-2017 Scrum.org, All Rights Reserved 5. Improve Collaboratively 15
  16. 16. © 1993-2017 Scrum.org, All Rights Reserved 16 Myth /Truth? Where are the PEOPLE in Kanban?
  17. 17. © 1993-2017 Scrum.org, All Rights Reserved 17 kanban doesn't encourage creating effective teams
  18. 18. © 1993-2017 Scrum.org, All Rights Reserved 18 kanban is all about manufacturing, software isn't manufacturing
  19. 19. © 1993-2017 Scrum.org, All Rights Reserved 19 Isn’t Scrum just Kanban with a bigger batch size?
  20. 20. © 1993-2017 Scrum.org, All Rights Reserved 20 Scrum is for … Kanban is for … kanban is all about manufacturing, software isn't manufacturing
  21. 21. © 1993-2017 Scrum.org, All Rights Reserved 21 Our Scrum team has evolved to become a Kanban team.
  22. 22. © 1993-2017 Scrum.org, All Rights Reserved 22 We do Kanban because we can't plan out for an entire Sprint.
  23. 23. © 1993-2017 Scrum.org, All Rights Reserved 23 Scrum is revolutionary; Kanban is evolutionary. Kanban always starts with what you got
  24. 24. © 1993-2017 Scrum.org, All Rights Reserved 24 kanban always starts with what you got
  25. 25. © 1993-2017 Scrum.org, All Rights Reserved 25 Kanban accepts and reinforces command and control / waterfall mindset
  26. 26. © 1993-2017 Scrum.org, All Rights Reserved 26 Where are the PEOPLE in Kanban?
  27. 27. © 1993-2017 Scrum.org, All Rights Reserved 27 Myth /Truth? Where are the PEOPLE in Kanban?
  28. 28. © 1993-2017 Scrum.org, All Rights Reserved Changes you can try in your Scrum teams 28
  29. 29. © 1993-2017 Scrum.org, All Rights Reserved Use a Kanban Board as your Sprint Backlog 29
  30. 30. © 1993-2017 Scrum.org, All Rights Reserved Make more of your processTransparent by making more policies explicit 30 THE Definition of Done: • Asdcasdc • Asdcasdca • sdcasdca • Asdca sdc • Asdca sdca • sdcasd ca • Asdcasdc • Asdcasdca • sdcasdca • Asdcasdc • Asdcasdca • sdcasdca
  31. 31. © 1993-2017 Scrum.org, All Rights Reserved Work Item Age / Fighting Zombies 31
  32. 32. © 1993-2017 Scrum.org, All Rights Reserved The Banana PeelTechnique 32
  33. 33. © 1993-2017 Scrum.org, All Rights Reserved Flow-based Sprint Planning • Leverage the Sprint Goal • You don’t need to plan out the entire Sprint • You can begin unplanned work part way through the Sprint • Work can flow across Sprint boundaries 33
  34. 34. © 1993-2017 Scrum.org, All Rights Reserved Flow-based Sprint Planning • Work planned for the first days of the Sprint by the DevelopmentTeam is decomposed by the end of this meeting, often to units of one day or less. • The Sprint Goal gives the DevelopmentTeam some flexibility regarding the functionality implemented within the Sprint.The selected Product Backlog items deliver one coherent function, which can be the Sprint Goal. The Sprint Goal can be any other coherence that causes the DevelopmentTeam to work together rather than on separate initiatives. • As the DevelopmentTeam works, it keeps the Sprint Goal in mind. In order to satisfy the Sprint Goal, it implements the functionality and technology. If the work turns out to be different than the DevelopmentTeam expected, they collaborate with the Product Owner to negotiate the scope of Sprint Backlog within the Sprint. 34
  35. 35. © 1993-2017 Scrum.org, All Rights Reserved Flow-based Sprint Planning 35
  36. 36. © 1993-2017 Scrum.org, All Rights Reserved Flow-based Daily Scrums 36 • Flow/Pull/Hebrew-mode –Work the Kanban board right to left • Focus on stories rather than going person by person • What work is blocked? • What work is about to violate our SLE? • What work are we not visualizing? • Where’s the bottleneck ?
  37. 37. © 1993-2017 Scrum.org, All Rights Reserved Flow-based Sprint Reviews • What is our current throughput? • How does this impact items in our Product Backlog? • Has our SLE changed? • What is our lead time? 37
  38. 38. © 1993-2017 Scrum.org, All Rights Reserved Flow-based Retrospectives Stop Start MoreLess Keep • Is our cycle time decreasing? • Did we meet our SLAs? • Ad Hoc (SLA violation) 38
  39. 39. © 1993-2017 Scrum.org, All Rights Reserved Helping more Scrum teams be Professional using Kanban, Helping Kanban teams be more Professional 39 Scrum Professional Kanban Professional • scrum.org/resources/blog/kanban-primer-scrum-teams • scrum.org/resources/blog/scrum-and-kanban-stronger- together • scrum.org/resources/blog/scrum-primer-kanban-teams • agilesparks.com/solutions/kanban/ • Professional Kanban Guide –WIP • Scrum.Org Professional Kanban for ScrumTeams -TBA
  40. 40. © 1993-2017 Scrum.org, All Rights Reserved Thank You 40
  41. 41. © 1993-2017 Scrum.org, All Rights Reserved Connect with the Scrum.org & AgileSparks community Twitter @scrumdotorg LinkedIn LinkedIn.com /company/Scrum.org Facebook Facebook.com /Scrum.org Blog Forums Scrum.org /Community RSS Scrum.org/RSS 41 Insights from AgileSparks’s team of Agile Coaches/Consultants

×