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.

Agile metrics

418 views

Published on

Finding the right metrics to help teams is sometimes difficult. Learn how one organization addresses this issue and helped to create a culture of experimentation.

Blog Post: https://www.spikesandstories.com/agile-metrics-team-useful/
YouTube: https://youtu.be/jlgXQtbvzls
High Resolution Slides: https://www.spikesandstories.com/wp-content/uploads/2018/01/AgileMetrics.pdf

Agile metrics

  1. 1. Agile Metrics Beyond Burndown Charts Tanner Wortham
  2. 2. What metrics will my teams find useful?
  3. 3. Who am I? • Lead Scrum Master at Study.com • Author of a popular agile blog at www.spikesandstories.com • U.S. Marine veteran
  4. 4. Corps Business • Reward failure. Someone who never fails probably isn’t pushing the envelope. • Aim for the 70% solution. It’s better to decide quickly on an imperfect plan than to roll out a perfect plan when it’s too late. • Experiment obsessively. Even the most successful organization will eventually stop winning if it doesn’t explore radically new approaches.
  5. 5. What metrics will my teams find useful?
  6. 6. What metrics will my teams find useful? Working software is the primary measure of progress.
  7. 7. How did the journey begin? • Inspired by Troy Magennis • Marrying thoughts from Mike Cohn and Jeff Sutherland • Leverage existing lean start up mindset • Created during a company hackathon
  8. 8. What are attributes of good metrics? • Within team’s influence • Trend based • Leading indicators • Have a credible story
  9. 9. What are attributes of bad metrics? • Just convenient to capture • Trailing indicators • Individual value based • Gaming leads to “bad”
  10. 10. What are our goals? • Inspire richer team conversations • Craft framework for team experimentation • Measure in multiple dimensions • Ensure tension between dimensions
  11. 11. Source: JIRA Formula = # Completed Points / # of Committed Points
  12. 12. Source: JIRA, Namely Formula = Velocity / Capacity
  13. 13. Source: Git
  14. 14. Source: HipChat
  15. 15. Source: JIRA
  16. 16. Source: JIRA
  17. 17. How does this help us experiment? Plan • Brainstorm • Hypothesize • Communicate 01 Do • Collect Data • Collaborate • Check In 02 Check • Decide Next Steps • Analyze Findings • Communicate 03 Done • Document Details • Plan for Next 04
  18. 18. What have we learned? • Getting started was easier than we expected • Leadership support isn’t enough • “The map is not the territory” • With data comes baggage • Gaining team engagement is challenging
  19. 19. What have we learned?
  20. 20. What’s next? • Measure outcomes at the org and team level • Explore ties between outputs and outcomes
  21. 21. Questions?
  22. 22. References • Corps Business by David Freedman • Agile Metrics at Øredev 2015 by Troy Magennis • An Appropriate Use of Metrics by Martin Fowler

×