Scrum is from Mars, Kanban is from Venus
•Download as PPTX, PDF•
1 like•173 views
Slides for the talk I gave at Beliminal's meetup group on 1st June 2020
Recommended
Recommended
More Related Content
Similar to Scrum is from Mars, Kanban is from Venus
Similar to Scrum is from Mars, Kanban is from Venus (20)
More from Dan Brown
More from Dan Brown (11)
Recently uploaded
Recently uploaded (18)
Scrum is from Mars, Kanban is from Venus
- 1. *actual book doesn’t exit
- 2. About Me Dan Brown Why am I here: I’m passionate about helping organisations transform, to improve service delivery to customers, and improve the working lives of people within the organisation. I happen to be a coach, teacher and speaker, focusing on Lean Kanban and Agile. I’m sometimes called KanbanDan I’m an Accredited Kanban Trainer, ICAgile Instructor and Certified Professional in Agile Coaching and Agile Facilitation. I am a Scrum.Org PSM III, PSK practitioner and lapsed Scrum Alliance CSM and CSP.
- 3. About You.. •Have you taken your brave pills today? •This presentation is now interactive with MentiMeter
- 4. Lets break some things first
- 5. Scrum is great for team based product delivery But not so easy to use for large multi-product service delivery flows…
- 6. A group of great individuals doesn’t magically make a great team Otherwise Manchester City would win the league every year, right?
- 7. Bigger isn’t always better England has 56 million people, NZ has 5 million. NZ 33 rugby wins to England’s 8 (1 draw)
- 8. A group of great teams doesn’t magically make great value flow
- 9. Lets look at it: Single scrum team Customer Single ScrumTeam Need Releasable Product Increment
- 10. ScrumTeam 1 Customer Need Non-ScrumTeam ScrumTeam 2 Non-ScrumTeam ScrumTeam 1 Non-ScrumTeam Releasable Product Increment SequentialTeam “Value Flow” (Eventually) (If we’re lucky)
- 11. Lets put it all back together again Get your buzzing hands ready…
- 12. What is Scrum for? “Jeff Sutherland and I developed the Scrum process for complex product development.” – Ken Schwaber www.controlchaos.com
- 13. “Scrum is … The Scrum Guide says: “Scrum is a framework for developing, delivering, and sustaining complex products”
- 14. What about Kanban? “Kanban is something you introduce to evolve an existing process” – David J Anderson on LinkedIn.com
- 15. Kanban says: “Kanban is a method for defining, managing, and improving services that deliver knowledge work” Essential Kanban Condensed – Carmichael and Anderson https://resources.kanban.university/guide/ - free ebook version
- 16. The Scrum.org Kanban Guide for Scrum teams says: “Kanban (n): a strategy for optimizing the flow of value through a process that uses a visual, work- in-progress limited pull system.” https://www.scrum.org/resources/kanban-guide-scrum-teams
- 17. Scrum is a delivery method Kanban is an improvement method
- 18. Scrum • Tells you how to deliver complex products • Says you should improve Kanban • Assumes you’re delivering service already already • Tells you how to improve
- 19. Scrum • Tells you a way to drive a car Kanban • Shows you how to improve your driving
- 20. Scrum • Tells you how to play the game Kanban • Tells you how to improve your game
- 21. Kanban is not agile • …but it is the alternative path to agility • Using Kanban to improve your services will lead you to become (more) agile • Benefits include: • High optionality of work selected • Fast delivery of work items • Focus on units of value delivery rather than units of work • Customer focus as a principle, and customer engagement needed • Inspect and adapt, but with more obvious things to inspect • Validated learning
- 22. Kanban and Scrum? •“Kanban and Scrum aren't even of the same genus”: • Scrum is a framework for developing, delivering, and sustaining complex products. • Kanban is a management method that prescribes the structure to evolve existing workflow processes. •You can apply Kanban to an instance of Scrum. Team framework to deliver a Product Service delivery improvement method
- 23. First steps to a wider • Kanban enables empirical improvement in Scrum teams • It brings measures and forecasting and Limited WIP • This brings more collaboration and improved throughput to “Using Kanban On Top Of Scrum” teams • Wow that is a mouthful, perhaps we can merge the two words together in a portmanteau, ‘Jedward’ style: • Let’s say it together, 1, 2, 3… KanRum! OK, maybe not
- 24. There problem with ScrumBan •There is no authoritative definition – it means whatever you want it to be •Most often means, “The bits of Scrum we like with the bits of Kanban that isn’t too hard to do” •You cannot hybrid Scrum and Kanban in the same way you cannot hybrid XP and Scrum in to XScrumP •Scrum is a framework to build in and around •If you use C++ in a Scrum team we don’t call it SC++rum do we?
- 25. Second steps to a • Kanban usually spreads (infects) upstream and downstream… we start looking at a wider picture beyond just their own team. • Everyone involved starts looking right to left across the whole org. • Soup to Nuts for service delivery • We start to care about the things the customer cares about, instead of the org chart… • Just like those end to end single scrum team orgs do.
- 26. ScrumTeam 1 Customer Need Non-ScrumTeam ScrumTeam 2 Non-ScrumTeam ScrumTeam 1 Non-ScrumTeam Releasable Product Increment (Eventually) Big organisation processes What if this is your team? Lets make it more visual
- 27. StarbanDan’s Coffee Shop Lets use an example we all know to explain a real Kanban Board Customer Queue Selected Order Payment Prep MilkBrew Coffee Lid Cup Sleeve Call Out Name Done2 2 10 4 2 3 3 4 Doing Done Doing Done Doing Done Doing Done Doing Done Doing Done Customer
- 28. StarbanDan’s Coffee Shop Lets use an example we all know to explain a real Kanban Board Customer Queue Selected Order Payment Prep MilkBrew Coffee Lid Cup Sleeve Call Out Name Done2 2 10 4 2 3 3 4 Doing Done Doing Done Doing Done Doing Done Doing Done Doing Done Customer Buffer Lanes WIP Limits
- 29. ScrumTeam 1 Customer Need Non-ScrumTeam ScrumTeam 2 Non-ScrumTeam ScrumTeam 1 Non-ScrumTeam Releasable Product Increment (Eventually) Big organisation processes What if this is your team?
- 30. Scrum Team 1 Scrum Team 1 Options Selected Discovery Build SIT TestDeployment UAT Pre-prod Testing Deployment Done4 4 4 4 2 3 3 4 Doing Done Doing Done Doing Done Doing Done Doing Done Doing Done Customer Non-Scrum TeamNon-Scrum TeamNon-Scrum Team Improved Live Service Big organisation processes Scrum Team 2 ∞ ∞
- 31. Options Selected Discovery Build SIT TestDeployment UAT Pre-prod Testing Deployment Done4 4 4 4 2 3 3 4 Doing Done Doing Done Doing Done Doing Done Doing Done Doing Done Customer Improved Live Service ∞ ∞
- 32. Options Selected Discovery Build SIT TestDeployment UAT Pre-prod Testing Deployment Done4 4 4 4 2 3 3 4 Doing Done Doing Done Doing Done Doing Done Doing Done Doing Done Customer Improved Live Service ∞ ∞
- 33. Why Add Scrum to Kanban? • Gives us structure - 5 Events • Gives us roles & accountabilities - 3 Roles • Gives us standard artefacts - 3 Artefacts • Gives us a framework to deliver, in which we can improve
- 34. • Visualising the whole system helps us see where it needs to be improved • Limiting WIP shifts us from focusing on working on our bit, to delivering he most value we can end to end •WIP Limits bring the pain forward and improve our delivery • (Real) Metrics make all this even better •PSK is a good step forward for us all to work together • Kanban classes can help you learn how to improve Concluding thoughts
Editor's Notes
- Team can act mostly scrum, but the higher level visualisation and WIP limits cause us to focus on service delivery, making the whole service become faster, more customer focused, and more agile.
- Team can act mostly scrum, but the higher level visualisation and WIP limits cause us to focus on service delivery, making the whole service become faster, more customer focused, and more agile.