Beyond WIP Limits (short version)

39
Beyond WIP limits Pawel Brodzinski @pawelbrodzinski

description

Limiting work in progress (WIP) is a concept widely popularized by Kanban, but in different forms it also exists in other agile approaches. Despite that, applying limits is a practice which many teams find either counterintuitive or non-value adding and eventually skip it. We should however start with answering a couple of basic questions. Why do we introduce limits in the first place? What do we get thanks to them? After all we don’t apply limits just to make our work less convenient, do we? The session will discuss limiting work in progress revealing a bit of mechanics of the concept and pointing false beliefs which we often embrace in software development teams. It will show how this mechanics can be exploited to improve our processes in both expected and unexpected ways. After the session you should be tempted to apply WIP limits in your process or, if they are already a part of the process, to adjust them accordingly. And most of all, you should know why and how limits are working, which will help you to make a decision when you should introduce them and how strictly a team should respect them.

Transcript of Beyond WIP Limits (short version)

Page 1: Beyond WIP Limits (short version)

Beyond WIP limits

Pawel Brodzinski

@pawelbrodzinski

Page 2: Beyond WIP Limits (short version)

Once upon a time…

Page 3: Beyond WIP Limits (short version)
Page 4: Beyond WIP Limits (short version)
Page 5: Beyond WIP Limits (short version)

Why?

Page 6: Beyond WIP Limits (short version)

100% utilization

Page 7: Beyond WIP Limits (short version)

That is so wrong

Page 8: Beyond WIP Limits (short version)

Cost of multitasking

Page 9: Beyond WIP Limits (short version)

Time to market

Page 10: Beyond WIP Limits (short version)

On a highway

Page 11: Beyond WIP Limits (short version)

In a call center

Page 12: Beyond WIP Limits (short version)

On a computer

Page 13: Beyond WIP Limits (short version)

Ball Flow

Game

Page 14: Beyond WIP Limits (short version)

No WIP Limits

Page 15: Beyond WIP Limits (short version)

Using WIP Limits

Page 16: Beyond WIP Limits (short version)

Why something that intuitive seems so counterintuitive when we talk about management?

Page 17: Beyond WIP Limits (short version)

…and they lived happily ever after

Page 18: Beyond WIP Limits (short version)

5O

WIP limits!

Page 19: Beyond WIP Limits (short version)
Page 20: Beyond WIP Limits (short version)
Page 21: Beyond WIP Limits (short version)

Why?

Page 22: Beyond WIP Limits (short version)

Slack time

Page 23: Beyond WIP Limits (short version)
Page 24: Beyond WIP Limits (short version)
Page 25: Beyond WIP Limits (short version)
Page 26: Beyond WIP Limits (short version)

We don’t live in ideal world

Page 27: Beyond WIP Limits (short version)

Automation

Page 28: Beyond WIP Limits (short version)

Code quality

Page 29: Beyond WIP Limits (short version)

Simple configuration

Page 30: Beyond WIP Limits (short version)

Self-balancing team

Page 31: Beyond WIP Limits (short version)

Slack time introduced by WIP limits drives continuous

improvement

Page 32: Beyond WIP Limits (short version)

Help others

Page 33: Beyond WIP Limits (short version)

Learn

Page 34: Beyond WIP Limits (short version)

Do nothing

Page 35: Beyond WIP Limits (short version)

Takeouts

Page 36: Beyond WIP Limits (short version)

100% utilization is a myth

1OO%

Page 37: Beyond WIP Limits (short version)

Introducing WIP limits results in improved efficiency

Page 38: Beyond WIP Limits (short version)

Slack time sets us on path of continuous improvement

Page 39: Beyond WIP Limits (short version)

Thank you

Pawel Brodzinski

blog.brodzinski.com

vsoft.pl

@pawelbrodzinski