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. For more information on preparing for the PSK I exam, visit our Professional Kanban PSK I™ Exam Prep.