• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Beyond WIP Limits (Lean Kanban Tour Edition)
 

Beyond WIP Limits (Lean Kanban Tour Edition)

on

  • 2,978 views

 

Statistics

Views

Total Views
2,978
Views on SlideShare
1,991
Embed Views
987

Actions

Likes
2
Downloads
28
Comments
0

11 Embeds 987

http://blog.brodzinski.com 808
http://brodzinski.com 106
http://feeds.feedburner.com 54
http://future-processing.com 9
http://translate.googleusercontent.com 3
http://www.newsblur.com 2
http://www.hanrss.com 1
http://127.0.0.1 1
https://si0.twimg.com 1
http://www.twylah.com 1
http://twitter.com 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Beyond WIP Limits (Lean Kanban Tour Edition) Beyond WIP Limits (Lean Kanban Tour Edition) Presentation Transcript

    • Beyond WIP limits Pawel Brodzinski @pawelbrodzinski
    • Hi, I’m PawelVSofthttp://vsoft.plSoftware ProjectManagementhttp://blog.brodzinski.comTwitter@pawelbrodzinski
    • Once upona time…
    • Why?
    • 100% utilization
    • Cost of multitasking Source: Gerald Weinberg, Quality Software Management: Vol. 1 System Thinking
    • Time to market
    • Catching up UM… HOW DOES THIS DARN CODE WORK, AGAIN?
    • Moremistakes Source: E. Ophir, C. Nass, A. Wagner:Cognitive control in media multitaskers
    • On a highway
    • In a call center
    • On a computer
    • At a conference
    • Ball FlowGame
    • No WIP Limits
    • Using WIP Limits
    • Total time: 26% betterAverage cycle time: 59% better Predictability*: 89% better *Standard deviation
    • Why something that intuitiveseems so counterintuitivewhen we talk aboutmanagement?
    • …and they livedhappily everafter
    • WIP limits! 5O
    • Average cycle time: 50% betterPessimistic scenario: 53% better Predictability*: 65% better *80th percentile
    • Why?
    • Slack time
    • Automation
    • Code quality
    • Simpleconfiguration
    • Self-balancingteam
    • Slack time introduced byWIP limits drives continuous improvement
    • When introducing WIP limits start with 2x average WIP Don Reinertsen
    • Cost of blocked work: 1% worseCost of idle capacity: 1% worseAverage cycle time: 28% better Source: Don Reinertsen, #lkce12 keynote
    • Are aggressiveWIP limitsuseful? 2O
    • What’s the useof slack time?
    • Idletimeonly?
    • Helpothers
    • Learn
    • Systemimprovements!
    • COST OF DELAYVALUE
    • Project andCOST OF DELAY product work VALUE
    • Project andCOST OF DELAY product work System improvements VALUE
    • Cost of blocked work: 1% worse
    • Cost of blocked work: 1% worse What’s the value of blocked or rejected work?
    • Cost of idle capacity: 1% worse
    • Cost of idle capacity: 1% worseIs capacity wasted or used to do something else?
    • Average cycle time: 28% better
    • Average cycle time: 28% better What happens to cycle time thanks to improvements?
    • Project andCOST OF DELAY product work System improvements VALUE
    • Takeouts
    • 100% utilization is a myth 1OO%
    • Introducing WIP limits results in improved efficiency
    • Slack time sets us on path of continuous improvement
    • Thank youSpecial thanks to Don Reinertsen Pawel Brodzinski blog.brodzinski.com vsoft.pl @pawelbrodzinski