Metrics are the tools we use (and misuse) to help us understand how we’re evolving. Used well, Metrics can give us feedback on our team’s experiments and help us become aware of problems sooner. Used poorly, they become a stick to beat the team into submission. It’s important to be careful when using them, because all metrics have cost, will introduce noise into the system, and might be gamed.
- Forget dumb productivity measures and focus on software delivery performance with Accelerate’s Four Key Metrics
- How to do a Retrospective using Flow Metrics
- Measure Cycle Time, Not Velocity
- The Five Traps of Performance Measurement
- We Cannot Measure Productivity
Misuse of Metrics
- Be careful how often you measure – measure too often and we oversample getting only noise
- Addressing Problems Caused by Agile Maturity Metrics
- How Accountants Kill Innovation
- I’m Sorry, But Those Are Vanity Metrics
- Scrumming the Scrum (the use of happiness as a Metric in Retrospectives)
- Measuring Happiness on the Team: What is Crisp?
- How Measuring Happiness Helped Us Build a Better Team
- Agile Teams: Don’t use happiness metrics, measure Team Morale the level of rigour supporting this is astonishing.
- How I Measure Scrum Team Morale
- Escape Velocity – Better Metrics for Agile Teams – Doc Norton
- Software Development Metrics Paperback – Dave Nicolette