Your SlideShare is downloading. ×
0
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Beyond WIP Limits (short version)
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Beyond WIP Limits (short version)

1,119

Published on

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 …

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.

Published in: Technology, Business
1 Comment
7 Likes
Statistics
Notes
  • It's great stuff can be shared with my team
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total Views
1,119
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
45
Comments
1
Likes
7
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Beyond WIP limits Pawel Brodzinski @pawelbrodzinski
  • 2. Once upona time…
  • 3. Why?
  • 4. 100% utilization
  • 5. That is so wrong
  • 6. Cost of multitasking
  • 7. Time to market
  • 8. On a highway
  • 9. In a call center
  • 10. On a computer
  • 11. Ball FlowGame
  • 12. No WIP Limits
  • 13. Using WIP Limits
  • 14. Why something that intuitiveseems so counterintuitivewhen we talk aboutmanagement?
  • 15. …and they livedhappily everafter
  • 16. WIP limits! 5O
  • 17. Why?
  • 18. Slack time
  • 19. We don’t livein ideal world
  • 20. Automation
  • 21. Code quality
  • 22. Simpleconfiguration
  • 23. Self-balancingteam
  • 24. Slack time introduced byWIP limits drives continuous improvement
  • 25. Helpothers
  • 26. Learn
  • 27. Donothing
  • 28. Takeouts
  • 29. 100% utilization is a myth 1OO%
  • 30. Introducing WIP limits results in improved efficiency
  • 31. Slack time sets us on path of continuous improvement
  • 32. Thank you Pawel Brodzinskiblog.brodzinski.com vsoft.pl @pawelbrodzinski

×