Inspecting and Adapting WIP Limits in Scrum with Kanban
Work in Progress (WIP) limits are crucial in managing flow and ensuring that Scrum Teams maintain a sustainable pace of work. Adjusting these limits at the right time is key to optimizing performance.
Exam Question
When is the most appropriate time for Scrum Teams practicing professional Scrum with Kanban to inspect and adapt their Work in Progress (WIP) Limits?
(choose the best answer)
A. Never. Once set, WIP Limits cannot be modified.
B. During the Sprint Retrospective.
C. Every day during Daily Scrum.
D. Anytime the team sees fit.
Correct Answer
B. During the Sprint Retrospective.
Explanation
Correct Answer
B. During the Sprint Retrospective:
The most appropriate time for a Scrum Team practicing professional Scrum with Kanban to inspect and adapt their WIP limits is during the Sprint Retrospective. This event is specifically designed for the team to reflect on their processes, including WIP limits, and to make any necessary adjustments to improve performance in the next Sprint. The Retrospective allows the team to consider the effectiveness of their current WIP limits in a structured environment, ensuring that changes are well-considered and agreed upon by all members.
Why Other Options Are Less Appropriate
A. Never. Once set, WIP Limits cannot be modified:
This is incorrect because WIP limits should be flexible and subject to change based on the team’s observations and experiences. Adapting WIP limits is essential to improving workflow.
C. Every day during Daily Scrum:
While the Daily Scrum is a time to inspect and adapt the team’s progress toward the Sprint Goal, it is not the ideal time to make structural changes like adjusting WIP limits. Such changes require careful consideration and should be done in a more reflective setting.
D. Anytime the team sees fit:
Although teams should feel empowered to make necessary adjustments, making changes to WIP limits without a structured discussion could lead to hasty decisions. The Sprint Retrospective provides a formal setting for these discussions.
Relevance to the PSK I Exam
Understanding when to inspect and adapt WIP limits is crucial for the PSK I exam. It demonstrates knowledge of how to manage workflow effectively and make improvements in a disciplined manner.
Key Takeaways
- The Sprint Retrospective is the most appropriate time for inspecting and adapting WIP limits, ensuring that changes are well-considered.
- WIP limits should be flexible and subject to change based on the team’s reflections and experiences.
- Making changes to WIP limits during the Retrospective allows for thoughtful discussions and team agreement.
Conclusion
The Sprint Retrospective is the ideal time for Scrum Teams practicing professional Scrum with Kanban to inspect and adapt their WIP limits. This approach ensures that changes are made thoughtfully and with the consensus of the entire team.

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
- 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?
- A Scrum Team’s service level expectation (SLE) is an input into the various Scrum events. In which event will SLE provide the most benefit towards achieving good flow?
