Starting Point: Team Size as Initial Upper Bound

If team size = 5:

A reasonable initial WIP cap is:

WIP ≤ 5

Meaning:

No more than 1 active story per person.
No multitasking.
No “half-started” work. On starting before finishing.

This is a safe initial constraint.

It immediately reduces concurrency.

But it is only a starting hypothesis.

The Real Control Variable Is Aging

Your goal is not “WIP = team size.”

Your goal is: Maintain story aging below threshold (e.g., ≤ 3–5 days).

WIP is the lever.
Aging is the signal.

So the correct approach is:

Set initial WIP limit (e.g., 5).
Observe aging behavior.
Adjust WIP to keep aging stable.

Why Team Size ≠ Optimal WIP

Even with 5 people:

If work is tightly collaborative, optimal WIP might be:

3 or 4

If work is highly independent, optimal WIP might be:

If specialists exist (e.g., 1 tester), effective WIP might be:

3–4

So team size gives you an upper bound.
Aging behavior tells you the real limit.

The Adjustment Logic

After 2–3 sprints, inspect:

% of stories exceeding aging threshold
85th percentile cycle time
Variability spread

If aging breaches remain high:

→ WIP is still too high.

Reduce it.

If WIP frequently under-utilized and aging very low:

→ Possibly raise slightly (but cautiously).

Practical Adjustment Example

Team size = 5

Start:
WIP limit = 5

After 2 sprints:

25% of stories exceed 5-day threshold.
85th percentile = 10 days.

Reduce WIP to 4.

After 2 more sprints:

Aging breaches drop to 10%.
85th percentile drops to 7 days.

You found a better operating zone.

The Utilization Perspective

If WIP ≈ team size and work is uneven:

Effective utilization approaches 90–100%.

That drives cycle time tail growth.

Often optimal WIP is:

70–80% of team size.

For a 5-person team:

3 or 4 active stories is often healthier.

Slack allows:

Swarming
Blocker resolution
Stabilization

The Strong Control Framing

Instead of saying: “WIP equals team size.”

Say: “We will start with a conservative concurrency cap and tune it to maintain our aging threshold.”

That sounds disciplined.

One Clean Rule

If:

% of items exceeding aging threshold > 15–20%

Then:

WIP is too high for system stability.

Important Behavioral Principle

Never increase WIP because:

“We have idle time.”

Idle time is stability margin.

If aging is under control and variability low, stability is working.

Frame as Calibration, not Guesswork

We will set initial WIP based on team size, then adjust based on exposure signals to maintain predictable flow.

Start with WIP ≈ team size (upper bound).
Then tune downward to maintain aging discipline and percentile compression.

WIP is the lever.
Aging is the sensor.
Cycle time percentile is the outcome.

Setting Initial WIP Limits