If new urgent work emerges during the Sprint, who must change the Work in Progress (WIP) Limits in the team’s definition of "Workflow"? (choose the best answer)

If new urgent work emerges during the Sprint, who must change the Work in Progress (WIP) Limits in the team’s definition of "Workflow"? (choose the best answer)
A . The Product Owner.
B. Work in Progress (WIP) Limits cannot be changed during a Sprint.
C. The Scrum Master.
D. No one. New urgent work is not a valid reason to change Work in Progress (WIP) Limits.
E. The Developers.

Answer: D

Explanation:

In case the item is pulled into the Sprint Backlog, then the Developers need to figure out whether they can actually start it right away. This depends on the WIP limits and the current WIP. If the team is at their WIP limit they shouldn’t pull in that new item until some room frees up.

The longer it might take to get a normal pull slot ready, the more pressure there might be to actually expedite this card. This means going beyond the current WIP limits and pushing this item along on top of the existing flow. The typical way to do this is NOT to change the WIP limit definition but to go above WIP and note a WIP exception. These exceptions can then be a topic for inspection and adaptation at the Sprint Retrospective.

Latest PSK-I Dumps Valid Version with 350 Q&As

Latest And Valid Q&A | Instant Download | Once Fail, Full Refund

Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments