We all know that having lots of work in process causes problems when it comes to your delivery rate.

If you're on a Scrum team, this can look like items getting carried over from sprint to sprint, nothing being ready until the very end of the sprint, no capacity to respond to emergency fixes, or every new user story taking longer and longer to complete. These can all be indicators that your Scrum team has too much WIP.

But before you start thinking you need to incorporate other techniques and frameworks that focus on limiting WIP—did you know that Scrum already had a WIP limiting mechanism built into the framework?

In this episode, learn to take advantage of the ways Scrum can guide your team to limit the amount of work they have in progress and deliver at a more consistent rate.

Connect with Agile Bites Host Phil Ledgerwood on LinkedIn

Visit our website