Kanban Product Management

How to Improve WIP Control

Learn to manage work in progress more effectively with three actionable techniques.

Practical Work-in-progress (WIP) control can significantly impact your product development process. By combining WIP limits with Total Work Item Age (TWIA) and using quadrant charts for visualization, you can ensure that your team stays focused and productive. This article (inspired by Benjamin Huser-Berta's work) will guide you through 3 actionable strategies to enhance workflow and boost your team's performance.

Limit Work in Progress without Work In Progress Limits

Control WIP with TWIA

Instead of using WIP limits alone, combine them with Total Work Item Age (TWIA). This method gives a fuller picture of your work in progress. You can prioritize tasks more effectively, considering the number of items and their age. This approach addresses older tasks and ensures work flows smoothly through your pipeline.

Use Quadrant Charts

Create a chart with TWIA on the X-axis and WIP on the Y-axis. Divide the chart into four quadrants using the average values of TWIA and WIP. This visualization helps you quickly see if you need to start new work or focus on finishing current tasks. By monitoring which quadrant yteam'sam's work falls into, you can make informed decisions that keep your workflow balanced and efficient.

Aim for Above Average WIP and Below Average TWIA

To optimize throughput and cycle time, keep WIP above average while maintaining TWIA below average. This balance ensures your team works fully without letting tasks age too long. This strategy has increased throughput and reduced cycle times, leading to a more productive and efficient workflow.

Algorithm AssignCardsToQuadrants

Input: List of Kanban cards with TWIA and WIP values
Output: Dictionary of quadrants with assigned cards

1. Initialize four empty lists for quadrants: 
   Quadrant1 (Below Average TWIA, Below Average WIP): 'Low TWIA, Low WIP'
   Quadrant2 (Above Average TWIA, Below Average WIP): 'High TWIA, Low WIP'
   Quadrant3 (Below Average TWIA, Above Average WIP): 'Low TWIA, High WIP'
   Quadrant4 (Above Average TWIA, Above Average WIP): 'High TWIA, High WIP'

2. Calculate the average TWIA (TWIA_avg) from the list of Kanban cards
3. Calculate the average WIP (WIP_avg) from the list of Kanban cards

4. For each card in the list of Kanban cards:
   a. If card.TWIA <= TWIA_avg AND card.WIP <= WIP_avg:
      i. Assign card to Quadrant1 (Low TWIA, Low WIP)
   b. Else if card.TWIA > TWIA_avg AND card.WIP <= WIP_avg:
      i. Assign card to Quadrant2 (High TWIA, Low WIP)
   c. Else if card.TWIA <= TWIA_avg AND card.WIP > WIP_avg:
      i. Assign card to Quadrant3 (Low TWIA, High WIP)
   d. Else if card.TWIA > TWIA_avg AND card.WIP > WIP_avg:
      i. Assign card to Quadrant4 (High TWIA, High WIP)

5. Return a dictionary with the quadrants and their assigned cards:
   { "Low TWIA, Low WIP": Quadrant1, 
     "High TWIA, Low WIP": Quadrant2, 
     "Low TWIA, High WIP": Quadrant3, 
     "High TWIA, High WIP": Quadrant4 }

End Algorithm

Have you tried any of these techniques to manage WIP in your team? Share your experiences and insights in the comments section. Your contributions can help others and boost your professional visibility.

If you found this helpful content, please clap. Clapping helps the Medium algorithm show this content to more product owners, and by participating, you contribute to our professional community.