# Seed only near-term work

Keep traceability to the user problem while varying detail by proximity to selection.

Duration: 5 min

Create items for the first thin slice and keep technical work tied to the end-to-end result. Refine items nearest selection; leave later options coarse until their priority and evidence improve.

**Failure mode:** mobilisation is renamed “Sprint Zero” and expanded into complete upfront design. Name preparatory work plainly and preserve an emergent backlog.

## kickoff-problem-backlog-m1-l3-reading

### Detail follows proximity

Keep the user need and outcome traceable from each first-slice item. Refine items nearest selection until the team can understand and size them. Leave distant options coarse and revisit them as priorities and evidence change.

The Scrum Guide describes ongoing refinement but no three-level maturity model or Sprint Zero.

### Worked example and transfer practice

All examples below are fictional teaching material. Use synthetic notes; no workplace or personal data is required or uploaded.

**Seed a coherent first slice.** The fictional repair service first tests whether callers can confirm an agreed visit. Near-term work includes showing the proposed window, recording acceptance and preserving the phone exception. ‘Introduce an AI route optimiser’ remains a coarse later option. Developers clarify and size the near-term work; the Product Owner orders it against the goal. Do not add invented precision to distant options.

**Try before reading the guide:** Write two near-term items and one coarse later option for the library case. Explain how the near-term pair tests the failed-collection outcome. Name one access or safety requirement that must remain in the first slice.

<details>
<summary>Practice review guide</summary>

The near-term items form a usable path and trace to an outcome. A collection confirmation without an exception route is incomplete. Later options remain revisable rather than promised scope.

</details>

## kickoff-problem-backlog-m1-l3-check

Public answer keys are intentional. This check does not establish competence.