WIP Limits: Lessons from the Trenches (Part 3 of 3)

NOTE: If you’ve been following my blog series “WIP Limits: How to Journey (safely) into the Unknown,” this webinar serves as the final installment.

In this webinar, I’ll share some practical advice on how to limit work in process (WIP) at the team and organizational levels.

During this discussion, you’ll learn: 

  • How Kanban systems can help you manage your WIP and set limits
  • Tips for implementing WIP limits at the team and organizational levels
  • Lessons learned from the trenches at LeanKit

Discover what works — and what doesn’t work so well — when you start putting theory into practice.

Helpful links:

Presentation slides: WIP Limits – Lessons From the Trenches PDF
WIP Limits: How to Journey (safely) into the Unknown – Part 1 of 3

WIP Limits: How to Journey (safely) into the Unknown – Part 2 of 3

Stephen Franklin

Stephen Franklin is CIO and co-founder of LeanKit. Before LeanKit, he led development teams in practicing Lean and Kanban as a Domain Architect at Healthtrust Purchasing Group and Chief Software Architect at eDoc4u. Follow Stephen on Twitter @leankitstephen.

2 thoughts on “WIP Limits: Lessons from the Trenches (Part 3 of 3)

  1. Great presentation.

    However, with regards to the question “what should the devs do if they hit their wip limit”, I disagree that the 2 options are “do nothing” or “help the downstream team”.

    The best way that teams can use slack capacity is to improve the system. Just because the downstream team is overloaded, it does not mean that they are actually the constraint to the system. If they are not, helping them is actually a wasteful activity. Slack capacity should be used to look at the entire system and use a kaizen step to improve it.

  2. Great series and video. I especially liked the WIP limiting at organisation level as it’s a challenge we have at my current client. The WIP resisting personas are great value – a light hearted way of leadership/management team to be authentic with themselves.

Leave a Reply