Is Velocity a Worthwhile Predictor?
2 likes688 views
This document discusses issues with using velocity as a predictor of productivity. It argues that velocity only measures a narrow portion of work and excludes important pre-tasks, post-tasks, and wait times that reduce productivity. Instead, it recommends measuring value and waste in the system, visualizing workflow problems, and using work limits to create flow and slack in order to improve productivity over relying solely on velocity metrics.
Is Velocity a Worthwhile Predictor?
- 1. Is Velocity a Worthwhile Predictor? J. Calvin Hoot @bitNomad
- 4. Answer Key Each cell stands for 1 business day Green == value add (do more of this) Red == waste (do less of this) @bitNomad
- 5. Story of a Story @bitNomad
- 6. Story of a Story @bitNomad
- 7. Story of a Story @bitNomad
- 8. Story of a Story @bitNomad
- 9. Story of a Story @bitNomad
- 10. What Are You Really Estimating? 12 / 48 = 25% of 9.5 weeks @bitNomad
- 11. What Are You Really Estimating? 12 / 48 = 25% of 9.5 weeks 6 / 42 = 14% of 8.5 weeks @bitNomad
- 12. What Are You Really Estimating? 12 / 48 = 25% of 9.5 weeks 6 / 42 = 14% of 8.5 weeks 17 / 53 = 32% of 10.5 weeks @bitNomad
- 13. What Are You Really Estimating? 12 / 48 = 25% of 9.5 weeks 6 / 42 = 14% of 8.5 weeks 17 / 53 = 32% of 10.5 weeks No matter how complex, it’s 9.5 +/- 1 week @bitNomad
- 14. What Are You Really Estimating? 12 / 48 = 25% of 9.5 weeks 6 / 42 = 14% of 8.5 weeks 17 / 53 = 32% of 10.5 weeks No matter how complex, it’s 9.5 +/- 1 week In practice, expect to see closer to 5% @bitNomad
- 15. Velocity Only Counts If You Remove pre-tasks: small stories, JIT design @bitNomad
- 16. Velocity Only Counts If You Remove pre-tasks: small stories, JIT design post-tasks: continuous deployment & testing @bitNomad
- 17. Velocity Only Counts If You Remove pre-tasks: small stories, JIT design post-tasks: continuous deployment & testing wait time: flow, staff balance @bitNomad
- 18. What to do instead? Measure your system for value and waste @bitNomad
- 19. What to do instead? Visualize your system to see workflow problems capacity = 6 capacity = 4 capacity = 6 throughput = 4 @bitNomad
- 20. What to do instead? Visualize the system to see workflow problems and use work limits to create flow and slack limit = 4 capacity = 4 capacity = 6 throughput = 4 @bitNomad
- 21. What to do with slack? @bitNomad
- 22. What to do with slack? @bitNomad
- 23. What to do with slack? @bitNomad
- 24. What to do with slack? @bitNomad
- 25. Thank You! 1. Measure your process. 2. Visualize your workflow. 3. Create flow and slack to improve your face. J. Calvin Hoot @bitNomad Lean Mindset SF meetup bitnomad.com image credits: planning poker, two hours, committed, traffic, learning, swarm, nothing, improve