WIP or Whipped?

Agile Disrupted

So, how good are you at prioritizing what you need to get done at a sustainable pace? How often do you realistically say "yes" to last minute commitments that come up and how often do you say "no" to promises that you know you can't keep?

Do you find yourself saying the following:

• I'm going to sacrifice sleep, to get all this done.
• I'm going to sacrifice meals, to get all this done.
• I'm going to sacrifice time with my friends & family, to get all of this done.
• I'm going to leave this partially done, so that I can get everything else done.

Now, flip that to Agile teams using WIP limits:

• Can WIP limits expose an Agile team's inability to prioritize?
• What happens when an Agile team blindly follows WIP limits and starts cheating their way around them?
• What happens when Agile teams run the risk of pulling in too much work against their rate of predictability?
• Can WIP limits alone help undone work?
• Can WIP limits implicitly encourage collaboration for a fragmented team?
• How comfortable is an Agile team saying "no" to work that is past their available capacity?
• Are we really embodying a Work/Life balance if team members are allocated at <50% utilizationWhat happens when an Agile team's clear and visible policies are disregarded by leadership?

WIP limits encourage a culture of work that is done before pulling in more work. The tool(s) we use doesn’t guarantee the culture we seek, but the people do.

Are we setting the example of the culture we seek from others?

Find out with newest guest speakers, Sviatlana Kopts and Ranjit Sellars, as we uncover what it means to "stop starting, and start finishing." 🔥