Metrics and Reports
2 minutes to read
Last Updated: Wed 24 May 2023 09:23
This page is in draft and may include errors or omissions. Please check the discussions for any pending updates and changes to the content or to suggest your own changes.
In order to understand how your team is doing we need to have metrics that we can monitor across all of [Company]. There are two focuses of this work, first is the Product/Project/Organisation focus and second is the Team focus.
- [EBM Guide]
Here are the key metrics that should be collected and made transparent for every Product/Project/Organisation.
- Customer Satisfaction - Some form of sentiment analysis to help gauge customer engagement and happiness with the product.
- Employee Satisfaction - Some form of sentiment analysis to help gauge employee engagement, energy, and enthusiasm.
- Defect Trend - Measurement of change in defects since the last measurement. A defect is anything that reduces the value of the product to a customer, user, or to the organization itself. Defects are generally things that don’t work as intended.
- Mean Time to Repair - The average amount of time it takes from when an error is detected and when it is fixed. This helps reveal the efficiency of an organization to fix an error.
- Release Stabilization - The time spent correcting product problems between the point the developers say it is ready to release and the point where it is actually released to customers. This helps represent the impact of poor development practices and underlying design and codebase.
- Deployment / Release Frequency - The number of releases per time period, e.g. continuously, daily, weekly, monthly, quarterly, etc. This helps reflect the time needed to satisfy the customer with new and competitive products.
At the team level we should focus on the flow of value to the stakeholders. For this to work we should collect and monitor the following:
- Work in Progress (WIP)- The number of work items started but not finished. Note the difference between the WIP metric and the policies a Scrum Team uses to limit WIP. The team can use the WIP metric to provide transparency about their progress towards reducing their WIP and improving their flow.
- Cycle Time - The amount of elapsed time between when a work item starts and when a work item finishes.
- **Work Item Age ** - The amount of time between when a work item started and the current time. This applies only to items that are still in progress.
- Throughput - The number of work items finished per unit of time.
Things that we should not monitor (but the Team can for their own edification if they desire):
- Story Points
- Remaining Work
- Original Estimate