Practice : Progressive Elaboration of Work
Purpose and Strategic Importance
Progressive Elaboration of Work is the practice of refining and detailing work just-in-time, based on the latest understanding and context. It enables teams to avoid premature decisions, reduce waste, and remain responsive to change.
By planning at the right level of detail, at the right time, teams balance foresight with flexibility. This helps to deliver faster, learn continuously, and maintain focus on value over volume.
Description of the Practice
- Backlog items begin as high-level intentions and are shaped progressively as they approach delivery.
- Elaboration includes clarification, slicing, estimation, dependency checks, and risk identification.
- Teams avoid investing time in refining distant backlog items that may change or never be built.
- The practice supports emergent design, discovery, and better use of team time.
- Artefacts evolve incrementally rather than being fully specified upfront.
How to Practise It (Playbook)
1. Getting Started
- Tag backlog items as “Now”, “Next”, or “Later” to signal refinement priority.
- Define working agreements for what makes a backlog item “ready” for sprint planning.
- Refine upcoming work collaboratively in regular refinement sessions.
- Capture only what’s needed to start valuable conversations, not full specifications.
2. Scaling and Maturing
- Align progressive elaboration with rolling-wave planning and roadmap shaping.
- Introduce just-in-time discovery spikes for higher-risk or unclear items.
- Decompose work iteratively, refining detail as technical and customer clarity increases.
- Use flow and planning metrics to track how far in advance work is refined and adjust accordingly.
3. Team Behaviours to Encourage
- Ask “What do we know now?” and “What do we still need to learn?” about each item.
- Avoid the urge to fully detail low-priority or uncertain backlog items.
- Encourage lightweight, evolving documentation over upfront specification.
- Review and revise items as new information emerges.
4. Watch Out For…
- Backlogs becoming cluttered with old, over-detailed items.
- Teams feeling pressure to define everything early for the sake of certainty.
- Discovery and refinement happening too late to enable smooth delivery.
- Delayed value due to “big design up front” approaches.
5. Signals of Success
- Backlog items are refined to an appropriate level based on proximity to delivery.
- Teams spend less time reworking or rewriting backlog items.
- Slicing and shaping of work improves incrementally over time.
- Planning is lean, adaptive, and focused on the most important decisions now.
- Teams move from ambiguity to clarity without becoming rigid or over-specified.