Applying Little’s Law in Scrum with Kanban
Little’s Law is a fundamental principle in queueing theory that can help teams understand the relationship between Work In Progress (WIP), throughput, and cycle time. However, its application in predicting future outcomes requires careful consideration.
Exam Question
Little’s Law is extremely valuable for directly predicting the future because it gives us a measure of what happened in the past? (Choose the best answer)
A. True – By understanding our cycle-time we can use Little’s Law to reduce our WIP limits.
B. False – Relying only on your cycle-time measurements may incorrectly influence you to cut your WIP limits.
Correct Answer
B. False
Explanation
Correct Answer
B. False:
Little’s Law provides valuable insights into the relationship between Work In Progress (WIP), throughput, and cycle time based on historical data. However, using it solely to predict future outcomes or to make decisions, such as reducing WIP limits, without considering the broader context can be misleading. Cycle time measurements reflect past performance, but they don’t account for future variability, changes in team capacity, or other influencing factors. Relying too heavily on past cycle times may lead to incorrect decisions, such as unnecessarily cutting WIP limits, which could impact team productivity and flow negatively.
Key Points on Little’s Law
- Understanding Historical Data: Little’s Law helps teams understand how WIP, cycle time, and throughput have interacted in the past, providing a baseline for how work has flowed through the system.
- Limitations in Prediction: While past data is informative, it is not always a reliable predictor of future performance, especially if the team faces new challenges or changes in workflow.
- Balanced Decision-Making: Decisions about WIP limits and workflow adjustments should be based on a combination of historical data, current observations, and anticipated future conditions, rather than solely on past cycle times.
Relevance to the PSK I Exam
Understanding the correct application of Little’s Law in Scrum with Kanban, and the limitations of using past cycle time data for future predictions, is essential for the PSK I exam. It demonstrates the ability to apply theoretical principles in a practical, context-aware manner.
Key Takeaways
- Little’s Law is valuable for understanding historical data but should not be solely relied upon for predicting future outcomes or making decisions about WIP limits.
- Decisions should be based on a combination of historical data, current observations, and future expectations.
- Careful consideration is needed when applying Little’s Law to ensure it supports, rather than hinders, effective workflow management.
Conclusion
While Little’s Law is a powerful tool for understanding the relationship between WIP, throughput, and cycle time, its application in directly predicting future outcomes should be approached with caution. Relying solely on past data may lead to incorrect decisions, such as unnecessary reductions in WIP limits.

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
- The team needs to work on a high priority urgent unplanned item, but they are at their WIP limit.
- Who owns the Kanban board in the Sprint Backlog?
- True or False: Cycle time is a direct leading indicator for the length of the Scrum Team’s feedback loop for a product backlog item.
- True or False: The purpose of a Scrum Team’s Service Level Expectation (SLE) is to allow teams to give each PBI a commitment to a due date as part of Sprint Planning.
- True or False: Scrum Events, Roles, Artifacts, and Rules are impacted when using Scrum with Kanban. For example, having a clear indicator of the age of active Sprint Backlog items may be beneficial during Daily Scrum, thereby positively impacting the decisions about how to Inspect and Adapt in the next day.
