# Bound the option before sizing it

Turn a broad request into the smallest coherent option that can test an outcome.

Duration: 5 min

Begin with the decision rather than the wish list. Name the user or beneficiary, the problem, an observable near-term milestone and the smallest coherent capability that could test it.

Then write explicit exclusions. Exclusions prevent plausible expectations from silently entering the estimate. The boundary is provisional: later evidence may reshape it.

**Practice:** For a reporting service, replace “build the complete analytics platform” with “enable two finance teams to reconcile two sources during one monthly close.” List mobile alerts and additional sources as exclusions.

## initial-estimates-m1-l1-reading

### Outcome boundary

Write five lines: beneficiary, problem, observable milestone, included capability and exclusions. Invite the people who understand value, use and implementation, but keep the artefact deliberately low fidelity.

The Scrum Guide supports the distinction between a goal, an emergent backlog and sizing by the people doing the work. It does not prescribe this five-line method.

### Worked example and transfer practice

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

**A bounded reconciliation option.** Fictional boundary: two finance teams compare exports from two sources during one monthly close and identify unmatched entries. Include importing the exports, showing mismatches and recording review decisions. Exclude automatic correction, additional sources and mobile alerts. The boundary gives the people doing the work something to inspect; it does not guarantee that the option is small or easy.

**Try before reading the guide:** Draft five lines for a maintenance handover: beneficiary, current problem, observable milestone, included capability and exclusions. Explain what would make the option incoherent if removed.

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

A usable boundary names an observable result and exclusions. ‘Improve maintenance in four weeks’ supplies a date but does not explain the capability or the evidence of improvement.

</details>

## initial-estimates-m1-l1-check

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