Active Management of Work in Progress

Overview

• What you’ll learn: Techniques for actively managing WIP, using Work Item Age as a management signal, swarming and pairing to unblock items, and when to cancel or de-scope work items.
• Prerequisites: Lessons 33–37.
• Estimated reading time: 13 minutes

Introduction

Setting WIP limits is necessary but not sufficient. WIP limits tell you when to pay attention. Active management tells you what to do about it. The Kanban Guide explicitly calls out “Active Management of Work Items in Progress” as one of the four practices — because without it, your board becomes a passive display of slow-moving items.

Work Item Age as a Management Signal

The single most useful metric for active management is Work Item Age. During each Daily Scrum, the team should ask about any item whose age exceeds the team’s average cycle time:

• Why is this item still in progress?
• Is it blocked? By what? Who can help?
• Has the scope grown since it was started?
• Should we split it into smaller items?
• Is it still the highest priority, or should we stop and work on something else?

Aging items are symptoms. The root causes are typically: unclear requirements, external dependencies, waiting for approvals, technical complexity discovered mid-work, or simply that the item was too large to begin with.

Swarming

When an item is aging, one powerful response is swarming: multiple team members focus on a single item to get it finished. This is the opposite of the traditional approach where each person works on their own item.

Swarming works because it reduces WIP (fewer items in progress), eliminates handoffs (the people who built it also test it), and creates shared knowledge (no one person is a bottleneck).

When to Stop and De-scope

Sometimes the right response to an aging item is to stop working on it. This is psychologically difficult — sunk cost fallacy makes us want to finish what we started. But if an item has been in progress for three times its expected cycle time, you need to seriously consider:

• Is the value still there?
• Can we deliver partial value?
• Should we split this into a smaller “shippable” item and a follow-up?
• Has the context changed since we started?

Flow-Focused Daily Scrum

Instead of the traditional “what did I do yesterday / what will I do today / any blockers” format, try a flow-focused Daily Scrum:

1. Walk the board right to left — start with items closest to Done.
2. Identify aging items — any item older than the team’s average cycle time gets attention.
3. Address blocked items — who can help unblock? Can we swarm?
4. Check WIP limits — are we at or near our limits? Should we pull new work or help finish existing work?

Key Takeaways

• WIP limits tell you when; active management tells you what to do.
• Work Item Age is your primary management signal.
• Swarm on aging items to reduce WIP and finish faster.
• Don’t fall for sunk cost — be willing to stop or de-scope.
• Walk the board right-to-left in Daily Scrum for flow-focused discussion.