One simple way to improve PI Planning: Make sure every feature can complete within two sprints.
Large features create:
- uncertainty
- coordination overhead
- delivery risk
Small features:
- flow more easily
- give faster feedback
- improve predictability
If your teams struggle during PI Planning, start here.
Large features destroy predictability. Small features enable it.
Why Large Work Breaks Flow
Control systems (like Kanban) depend on fast feedback.
Large work items delay feedback by design.
When work is large:
- Aging thresholds fire too late
- WIP limits become theoretical
- Decisions are deferred or avoided
- Escalation replaces correction
The system appears stable until it suddenly isn’t.
Large features hide problems until recovery is expensive.
Smallness Enables Early Intervention
Aging signals only work when they are meaningful and actionable.
If an item is expected to take:
- Days → aging in days is meaningful
- Weeks → aging in weeks is actionable
- Months → aging is too slow to govern
Small work creates dense signals.
Problems surface early, while corrective action is still cheap.
Smallness Makes Stopping Possible
Stopping work is one of the most important control actions in Kanban.
It is also one of the hardest.
Large work items:
- Accumulate sunk cost
- Attract political protection
- Become emotionally charged
- Resist termination
Small work:
- Has lower sunk cost
- Is easier to abandon
- Preserves optionality
If work cannot be stopped once started, it is too large to govern.
Features should be small enough that:
- They complete within a short delivery horizon
- Dependencies are exposed early
- Learning is not deferred to the end
- Aging thresholds trigger real decisions
A practical heuristic:
If a feature cannot reasonably complete within two iterations, it is too large.
Size Is a Design Choice
Work does not arrive at a fixed size.
Size is shaped by:
- How problems are framed
- How scope is bounded
- How learning is staged
- How risk is isolated
When organizations say: “Our work is just big”
What they usually mean is: “We designed it that way.”
Smallness Reduces Governance Load
Large work requires:
- Reviews
- Exceptions
- Escalations
- Oversight
Small work governs itself.
- Triggers fire earlier.
- Corrections are cheaper.
- Meetings shrink or disappear.
Designing for smallness is a governance strategy, not just a delivery tactic.
The Cost of Ignoring Size
When size is not designed deliberately:
- Limits lose force
- Aging loses meaning
- Triggers fire too late
- Governance regresses to ceremony
This is not a failure of discipline. It is a failure of design.
Making sure every feature is small enough to enable early corrective action is one of the simplest ways to improve PI Planning.