Practice communicating Agile team metrics in English: velocity, cycle time, lead time, throughput, and sprint burndown.
0 / 8 completed
1 / 8
How would you describe 'velocity' in a sprint review?
Velocity measures how many story points a team completes per sprint. It is averaged over 3-5 sprints and used to forecast how much work fits into future sprints.
2 / 8
What is 'cycle time' in Agile metrics?
Cycle time measures how long an item takes from 'work started' to 'work done'. Shorter cycle times indicate faster flow through the team's process.
3 / 8
Which sentence correctly interprets a burndown chart?
When the actual line is above the ideal line on a burndown chart, the team has more remaining work than planned at that point — they are behind schedule.
4 / 8
What does a high 'lead time' indicate about a team's process?
Lead time measures from when a request enters the backlog to when it is delivered. High lead time indicates delays in prioritization, development, or deployment.
5 / 8
How would an engineer explain 'escaped defects' in a sprint report?
Escaped defects are bugs that bypassed testing during the sprint and were discovered after release — by QA in production or by customers. Tracking them helps improve quality processes.
6 / 8
What does 'throughput' measure in Kanban/Agile contexts?
Throughput is the number of work items (stories, tasks, bugs) a team completes per time period. Unlike velocity, it does not depend on story point estimates.
7 / 8
Which phrase would you use to communicate a sprint goal was not met?
Professional sprint communication explains what was not achieved, what caused it (without blame), and what the impact is. 'We failed' is too blunt; 'backlog was not cleared' misunderstands sprint goals.
8 / 8
What is 'WIP limit' and how would you explain it?
WIP (Work In Progress) limits constrain how many items can be in a given workflow stage simultaneously. They expose bottlenecks and encourage finishing work before starting new items.