Agile Metrics & Reporting Flashcards
7 cards from real CAE practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Agile Metrics & Reporting flashcards as text
A team wants to measure how much value they deliver relative to the effort spent. Which metric BEST captures this?
Answer: Business value delivered per story point or per sprint
Tracking business value delivered per unit of effort (story point or sprint) directly measures efficiency of value creation, not just output volume.
In agile reporting, what does a 'flat' burndown line for several days indicate?
Answer: No work is being completed, suggesting a blocker or impediment
A flat burndown line means remaining work is not decreasing, which almost always signals a blocker, dependency issue, or team impediment that needs resolution.
Which agile metric is MOST useful for measuring the health of an organization's continuous delivery pipeline?
Answer: Deployment frequency
Deployment frequency (one of the DORA metrics) measures how often the team releases to production, directly reflecting CI/CD pipeline maturity and agility.
A team is asked to reduce the time between identifying a production bug and releasing a fix. Which DORA metric directly tracks improvement in this area?
Answer: Mean time to restore (MTTR)
Mean Time to Restore (MTTR) measures how quickly a team recovers from production failures, directly tracking the team's incident response and fix cycle.
What does a team's 'change failure rate' tell stakeholders about their delivery process?
Answer: The percentage of deployments that cause production failures or require rollback
Change failure rate measures the proportion of deployments that result in degraded service or require hotfixes, indicating the reliability of the delivery pipeline.
Which practice BEST supports continuous improvement of agile metrics and reporting over time?
Answer: Regularly reviewing which metrics are being acted upon and retiring those that don't drive decisions
Metrics should be reviewed periodically; those that no one uses to make decisions are waste and should be dropped in favor of metrics that drive actionable improvements.
An agile coach notices a team tracks 12 different metrics each sprint but rarely acts on any of them. What is the MOST appropriate recommendation?
Answer: Reduce to 3-5 actionable metrics that directly connect to team goals
Fewer, well-chosen metrics that drive actual decisions are far more valuable than a large collection of metrics that create noise without prompting action.