Understanding Lagging Indicator Metrics in Scrum with Kanban
Lagging indicators are metrics that reflect what has already occurred in the past. These metrics are useful for assessing the effectiveness of processes but are not predictive of future performance.
Exam Question
Which of the following are lagging indicator metrics?
(choose the best three answers)
A. Work Item Aging.
B. Throughput.
C. Cycle Time.
D. Work in Progress.
E. Velocity.
Correct Answers
B. Throughput.
C. Cycle Time.
E. Velocity.
Explanation
Correct Answers
B. Throughput:
Throughput measures the amount of work completed over a specific period of time. It is a lagging indicator because it reflects the work that has already been finished, providing insights into how productive the team was during that period.
C. Cycle Time:
Cycle time tracks how long it takes for a work item to move from start to completion. It is considered a lagging indicator because it measures the duration of past work, helping teams understand how quickly they have been able to complete tasks historically.
E. Velocity:
Velocity measures the amount of work a Scrum Team completes during a Sprint. It is a lagging indicator because it looks at what has been accomplished in previous Sprints, providing a historical view of the team’s capacity.
Why the Other Options Are Not Correct
A. Work Item Aging:
Work Item Aging is considered a leading indicator because it tracks how long a work item has been in progress, helping to identify items that may need attention before they are completed.
D. Work in Progress:
Work in Progress (WIP) refers to the number of items currently being worked on. While WIP can influence future outcomes, it is not a lagging indicator as it reflects the current state of work rather than past performance.
Relevance to the PSK I Exam
Understanding the distinction between lagging and leading indicators is essential for the PSK I exam. Lagging indicators provide valuable insights into past performance, helping teams assess how effective their processes have been.
Key Takeaways
- Lagging indicators reflect past performance, providing insights into how effectively work has been completed.
- Throughput, Cycle Time, and Velocity are key lagging indicators in Scrum with Kanban.
- Recognizing the difference between leading and lagging indicators helps teams better manage and predict workflow outcomes.
Conclusion
Throughput, Cycle Time, and Velocity are important lagging indicators in Scrum with Kanban. These metrics help teams assess their past performance and make informed decisions to improve future workflows.

Get ready for the official PSK I exam
115 PSK I practice questions, each with an in-depth explanation like the one above.
- Practice Mode: study at your own pace and choose the test length.
- Mock Exam Mode: 45 random questions in 60 minutes, like the real exam.
$29 is ScrumPrep's one-time price. The official PSK I exam fee ($200) is paid separately to Scrum.org.
More PSK I exam questions
- When is the most appropriate time for Scrum Teams practicing professional Scrum with Kanban to inspect and adapt their Work in Progress (WIP) Limits?
- How does Kanban for Scrum Teams maximize value delivered?
- Your Scrum Team’s cycle time is currently 8 days or less with 85% confidence. The team has set the Service Level Expectations (SLE) accordingly. If an item in progress has just aged past your dataset’s 50th percentile, what can we say about the chance it will fail to meet the team’s 8-day SLE?
- When using Kanban, it is useful to have explicit policies. What existing elements in the Scrum Guide might be used as explicit policies?
- What is the best chart (analytic) to determine “When will it be finished?” for a single item in the Product Backlog?
