Product Management — All about Metrics
Medium | Mar 02, 2022
Comparison between Facebook & Twitter and their use of Engagement & Growth Metrics
What makes a good metric?
(3) Rate or Ratio
(4) Correlation vs. Causation
Exploratory vs Reporting Metrics
Methods to select your perfect metric
HEART = Happiness, Engagement, Adoption, Retention, Task (Kerry Rodden)
Across these dimensions, you will identify goals, signals, and metrics to measure how well your product is doing.
Goal = something the user is trying to do or something you are trying to help them to do
Signal = a change in user behavior that indicates that the user is achieving the goal
Metric = a way to measure signal and quantify how much user behavior has changed
Concludes with a walk you through an example for an imaginary product.
Author = Alaa MohyEldin
Epic and release burndown
Cumulative flow diagram
Author = Dan Radigan
What are Scrum Metrics and KPIs?
Scrum metrics and KPIs are part of a broader family of agile KPIs. Agile Metris include lean metrics, which focus on the flow of value from an organization to its customers, and Kanban metrics, which focus on workflow and getting tasks done. While most agile metrics are applicable to scrum teams, scrum-specific metrics focus on predictable software delivery, making sure scrum teams deliver maximum value to customers with every iteration.
Scrum KPIs have three major goals:
- To measure deliverables of the scrum team and understand how much value is being delivered to customers.
- To measure effectiveness of the scrum team; its contribution to the business in terms of ROI, time to market, etc.
- To measure the scrum team itself in order to gauge its health and catch problems like team turnover, attrition and dissatisfied developers.
Scrum Metrics—Measuring Deliverables
1. Sprint Goal Success
2. Escaped Defects and Defect Density
3. Team Velocity
4. Sprint Burndown
Scrum Metrics—Measuring Effectiveness
1. Time to Market
3. Capital Redeployment
4. Customer Satisfaction
Scrum Metrics—Monitoring the Scrum Team
1. Daily Scrum and Sprint Retrospective
2. Team Satisfaction
3. Team Member Turnover
Scrum Reporting—Which Metrics to Report to Stakeholders?
- Sprint and release burndown—Gives stakeholders a view of your progress at a glance.
- Sprint velocity—A historic review of how much value you have been delivering.
- Scope change—The number of stories added to the project during the release, which is often a cause of delays (many agile tools can show this automatically).
- Team capacity—How many developers are on the team full time? Has work capacity been affected by vacations or sick leave? Developers pulled off to side projects?
- Escaped defects—provides a picture of how your software is faring in production.
The Missing Scrum Metric—Software Quality
Author = Sealights