Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Why Limit WIP?

8,304 views

Published on

Why Limit WIP?
-Why it's important
-Why it's hard
-What you can do about it

Published in: Software, Technology, Business
  • Your opinions matter! get paid BIG $$$ for them! START NOW!!..  https://tinyurl.com/realmoneystreams2019
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Earn $500 for taking a 1 hour paid survey! read more...  https://tinyurl.com/realmoneystreams2019
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

Why Limit WIP?

  1. 1. • Why it’s important • Why It’s hard • What you can do about it Chris Hefley, CEO of LeanKit @indomitableHef Kanban: An Evolutionary Approach to Agility Why Limit WIP?
  2. 2. Chris Hefley, CEO and Co-founder of LeanKit, is a practitioner and thought leader in the global Lean/ Kanban community. In 2011, he was nominated for the Lean Systems Society’s Brickell Key Award. After years of coping with “broken” project management systems in the world of software development, Chris helped build LeanKit as a way for teams to become more effective. Prior to LeanKit, Chris worked with globally distributed teams in leadership positions at HCA Healthcare and IMI Health. He believes in building software and systems that make people’s lives better and transform their relationship with work. follow @indomitableHef ABOUT CHRIS HEFLEY
  3. 3. What is Work-In-Process? all materials and partly finished products that are at various stages of the process Value Demand that has been started, but is not yet providing value to the customer
  4. 4. What is Work-In-Process? Total Story Lead Time 30 days Development Time 5 Days (~ 15%) Testing Time 2 Days Defect Rework 2 Days Release / DevOps Time 1 Day Blocked and Waiting Time 9 Days Waiting Time 3 Days Waiting Time 8 Days By Troy Magennis, FocusedObjective.com – used by permission
  5. 5. What is Work-In-Process? Total Story Lead Time 30 days Development Time 5 Days (~ 15%) Testing Time 2 Days Defect Rework 2 Days Release / DevOps Time 1 Day Blocked and Waiting Time 9 Days Waiting Time 3 Days Waiting Time 8 Days By Troy Magennis, FocusedObjective.com – used by permission
  6. 6. What is Work-In-Process? Total Story Lead Time 30 days Story / Feature Inception 5 Days Waiting in Backlog 25 days System Regression Testing & Staging 5 Days Waiting for Release Window 5 Days “Active Development” 30 days Pre Work 30 days Post Work 10 days
  7. 7. Total Story Lead Time 30 days Story / Feature Inception 5 Days Waiting in Backlog 25 days System Regression Testing & Staging 5 Days Waiting for Release Window 5 Days “Active Development” 30 days Pre Work 30 days Post Work 10 days 9 days (70 total) approx 13% What is Work-In-Process?
  8. 8. Partially Done Work Has Zero Value
  9. 9. 1. Visualize your Work 2. Limit your Work in Process 3. Focus on Flow 4. Continuous Improvement What is Kanban?
  10. 10. This is Greek to me. So are many/most project deliverables to non-specialists
  11. 11. A picture translates complexity into a simple pattern we can all digest
  12. 12. Ready In Process Done Development Test Done DeployIn Process Done F1 F2 F3 F4 D1 F5 (3) (3) (6) - Daniel and Stephen, Developers Yay! More Codez to write! This queue replenishment process is a example of “Push” - Jon (Product Manager) It’s my job to replenish the ready queue – I prioritize the top 6 items every 2-3 days Day 1
  13. 13. In Process Done Development Test Done DeployIn Process Done F1 F2 F3 F4 D1 F5 (3) (3)Ready (6) - Daniel and Stephen, Developers Finished One! Day 2
  14. 14. In Process Done Development Test Done DeployIn Process Done F1F2 F3 F4 D1 F5 (3) (3)Ready (6) F6 F7 F8 F9 - Chris (Tester) Now I have something to pull - Jon (Product Manager) Better replenish the queue… Day 3
  15. 15. In Process Done Development Test Done DeployIn Process Done F1F2 F3 F4 D1 F5 (3) (3)Ready (6) F6 F7 F8 F9 - Chris (Tester) This one is ready to deploy… Day 4
  16. 16. In Process Done Development Test Done DeployIn Process Done F1F2F3 F4 D1 F5 (3) (3)Ready (6) F6 F7 F8 F9 - Scott (DevOps) I’m on it… Day 5
  17. 17. In Process Done Development Test Done DeployIn Process Done F1F2F3 F4 D1 F5 (3) (3)Ready (6) F6 F7 F8 F9 Day 6
  18. 18. In Process Done Development Test Done DeployIn Process Done F1F2F3 F4 D1F5 (3) (3)Ready (6) F6 F7 F8 F9 - Chris (Tester) This one isn’t working… I’ll go ahead and pull some more to test… Day 7
  19. 19. In Process Done Development Test Done DeployIn Process Done F1F2 F3 F4 D1F5 (3) (3)Ready (6) F6 F7 F8 F9 F10 D2 F11 - Daniel and Stephen, Developers Rock and Roll… We’ve been very productive these last couple of days Day 8
  20. 20. In Process Done Development Test Done DeployIn Process Done F1F2 F3 F4 D1 F5 (3) (3)Ready (6) F6 F7 F8 F9 F10 D2 F11 - Daniel and Stephen, Developers Oops…can’t do that…it would break the WIP limit What can we do to help? F2 is broken… Ok, we’re on it Day 9
  21. 21. In Process Done Development Test Done DeployIn Process Done F1 F2 F3F4 D1 F5 (3) (3)Ready (6) F6 F7F8 F9 F10 D2 F11 F12 Work is flowing nicely now… Day 10
  22. 22. In Process Done Development Test Done DeployIn Process Done F1 F2 F3 F4 D1 F5 (3) (3)Ready (6) F6 F7 F8 F9 F10 D2 F11 F12 - Scott (DevOps) Now we’re really getting some stuff done! Day 11
  23. 23. Why Kanban Systems Work 1) The means to observe the flow of work 2) The mechanics to improve the flow of work (WIP Limits, Explicit Policies) 3) The evidence to show improvement, run experiments, and make adjustments A KANBAN SYSTEM GIVES YOU
  24. 24. From the Book: Stop Starting, Start Finishing, by Arne Roock
  25. 25. Three Kinds of WIP Limits • Personal WIP Limits • Team (Execution) WIP Limits • Organizational (Structural) WIP Limits
  26. 26. The Zeigarnik effect: When we finish tasks, we get closure and move on. When we don’t finish tasks—we don’t.
  27. 27. Managing Team (Execution) WIP Limits • Why: To Improve Flow • Challenges: –Variability –Constraints –Personal WIP
  28. 28. Lowering WIP Surfaces Problems From the book: Implementing Lean Software Development: From Concept to Cash by Mary Poppendeick and Tom Poppendeick
  29. 29. Managing Organizational (Structural) WIP Limits • Why: Clear Focus, Limit Options to increase the chance of achieving goals • To Make It Work –Limit your options –Systems Thinking –Watch for Hidden WIP
  30. 30. Limiting WIP at LeanKit
  31. 31. The Focused Intent
  32. 32. Standup Meetings, Kanban-Style
  33. 33. 1. What are we going to finish today? 2. What is needed to push this item over the line? 3. Is there any hidden WIP? All work is the Team’s Work
  34. 34. Resources • Stop Starting, Start Finishing, by Arne Roock • available on Amazon.com
  35. 35. Resources • The Phoenix Project, a Novel About DevOps, IT, and Helping Your Business Win, by Gene Kim, Kevin Behr, and George Spafford • available on Amazon.com
  36. 36. Resources • Why Limit WIP: We are Drowning in Work, by Jim Benson • Available in a 2-3 weeks at moduscooperandi.com
  37. 37. Resources • KANBAN Roadmap: How to Get Started in 5 Steps, by Chris Hefley and Liz Llewellyn • Available at the LeanKit booth at PathToAgility 2014 and at LeanKit.com • Download the electronic copy at http://leankit.com/path-to-agility

×