Velocity can help a team plan, but it creates problems when leaders use it to judge performance. In this episode, Brian Milner and Scott Dunn explain why that shift happens so often and what leaders should pay attention to instead. Overview Velocity is one of the most misunderstood metrics in Agile. Used well, it helps a team forecast and make planning decisions. Used poorly, it becomes a productivity score that encourages inflated estimates, unhealthy comparisons, and a focus on output rather than value. In this episode, Brian and Scott discuss why leaders often reach for velocity, why it gives them the wrong signal, and how teams can reconnect measurement to outcomes, learning, and business impact. They also explore how AI is making this issue more urgent by increasing delivery speed while putting even more pressure on leaders to ask whether teams are building the right things. References and resources mentioned in the show: Scott Dunn #35: Metrics with Lance Dacy Rethink the Refinement Session: Less Time, Better Outcomes by Mike Cohn The Cost of Change Curve Is Outdated by Mike Cohn Subscribe to the Agile Mentors Podcast Want to get involved? This show is designed for you, and we’d love your input. Enjoyed what you heard today? Please leave a rating and a review. It really helps, and we read every single one. Got an Agile subject you’d like us to discuss or a question that needs an answer? Share your thoughts with us at [email protected] This episode’s presenters are: Brian Milner is a Certified Scrum Trainer®, Certified Scrum Professional®, Certified ScrumMaster®, and Certified Scrum Product Owner®, and host of the Agile Mentors Podcast training at Mountain Goat Software. He's passionate about making a difference in people's day-to-day work, influenced by his own experience of transitioning to Scrum and seeing improvements in work/life balance, honesty, respect, and the quality of work. Scott Dunn is a Certified Enterprise Coach and Scrum Trainer with over 20 years of experience coaching and training companies like NASA, EMC/Dell Technologies, Yahoo!, Technicolor, and eBay to transition to an agile approach using Scrum.

Ask this episode

“What did the council decide on item 42?” — answered with the speaker and the moment.

Transcript

Related