From Scrum To Flow
This document discusses transitioning from a Scrum framework to a Kanban/flow approach. It defines flow as a pull system that focuses on regular delivery of value at a sustainable pace by optimizing work from beginning to end. Key aspects of flow/Kanban discussed include visualizing the workflow, limiting work-in-progress, making policies explicit, and improving collaboratively using data. Metrics like deployment frequency, change failure rate, mean time to recovery, and lead time are emphasized for achieving "escape velocity." Continuous delivery is also discussed as enabling easy deployments at any time through practices like infrastructure as code, robust continuous integration, and blue-green deployments. Adopting a flow approach requires professionals skilled in test-
From Scrum To Flow
- 1. From Scrum To Flow Yannick Grenzinger
- 2. What is Scrum for you ?
- 4. Sprint - Do we try to maximise team utilization ? - How do we finish ? - Can we maintain velocity ? - Is velocity only a team indicator ? - Is it efficient ?
- 6. Flow A pull system that focus on a regular delivery of value at a sustainable pace by optimising work from beginning to end Kanban + Continuous Delivery
- 8. What is Kanban for you ?
- 9. Core Principles - Start With What You Do Now - Respect the Current Process, Roles & Responsibilities - Agree to Pursue Incremental, Evolutionary Change - Encourage Acts of Leadership at All Levels
- 10. Core Properties - Visualize the workflow - Manage flow - Limit WIP - Make Process Policies Explicit - Improve Collaboratively (and with data)
- 12. Limiting WIP : -> reduces queues -> reduce waste -> improve quality
- 13. Prez flowcon (ex Lean kanban France 2015) https://fr.slideshare.net/don600/reinertsen-lk-france-2015-11-415
- 14. Data Driven
- 15. Escape velocity - How to accelerate Four key metrics from “State of devops report” ➔ Deployment Frequency - multiple deploys per day ➔ Change Failure Rate - 0-15% ➔ Mean Time To Recovery - less than one hour ➔ Lead (Cycle) Time for Change - less than one hour
- 18. Deeper into the rabbit hole Notebook explanations of some science behind Kanban metrics https://observablehq.com/@troymagennis The Economic Impact of High System Utilization https://observablehq.com/@troymagennis/the-economic-impact-of-high-system-utiliz ation Impact of Multiple Team Dependencies in Software Development https://observablehq.com/@troymagennis/impact-of-multiple-team-dependencies-in- software-developm
- 19. Measuring the full product dev flow http://www.flow.hamburg/de/2014/06/kanban-lead-time-updated/
- 20. Useful charts
- 24. What is Continuous Delivery ?
- 27. For that you need - Infra as a Service (IaaS, PaaS) - Infra as Code - Capacity to deliver easily at any time ! - Robust and Scalable Continuous Integration - Trunk Based Development (or Octopus) - Feature Toggle => Feature Branching (instead of git branching) - Blue - Green Deployment - Canary Release But moreover ...
- 28. You need professionals - Test Driven Development - Pair programming / Mob Programming - Contract Testing - Domain Driven Design - Living Documentation
- 29. Conclusion: Going from Scrum to Flow is not easy
- 30. Many books but ...
- 31. Questions ?