- to answer questions
- to make better business decisions
- to come conversations and insights to help teams succeed
use multiple metrics
- never rely on a single metric
good metrics should surprise you every now and then
- they generate questions as well, not just answers
- What should we do?
- When should we do it?
- What should we do next?
- How many customers have we gained this month?
- How much are they spending?
- Which features are they using the most?
- How long do people stay with us as customers?
- Do they recommend us to their friends?
- failure demand
operational metrics (hygiene factors)
- How much do we have left to do this week/month/year?
- How much time do we have to finish this?
- How long does it take us to deliver things?
- Delivery rate, Cycle time
- How fast are we going?
- the number of work items that were completed during a particular period of time
helps you become more predictable
Story points & velocity
- Are our estimates really working?
- Lead time
- to base on historical data and the metrics
- a high amount WIP?
- no focusing
- quality decease
- queues in process visible?
- unexpected events?
- way for Team improving
important for each Team role
- faster meeting!
- realistic expectation & promises
improve planning and forecast
use it for short term predictions
- How many stories can we complete in the next sprint?
- How much can we get done in the next two weeks?
for long term predictions
- How long will it take?
- When are we going to complete this project/functionality/group of stories?
to validate experiments
- Current situation
- Our hypothesis
- Expected results
- How to measure our results
count the number of work items that have been completed in a fixed period of time
split throughput by work item type
- follow a different process
- the same process with different speed
- Average & median
- Standard deviation
- Min and max
- the most common throughput
- Probability percentiles