Skip to content
Astera Technology

Bound a first release around supported cases

Keep excluded cases on a declared route instead of implying universal coverage.

Plan from the supplied facts

Fictional proposed release handles four standard case kinds A–D in 4 hours. Exceptional kind E requires eight additional hours. The owner’s planning assumption retains an existing manual route for E until its automated work is included. E cannot enter the limited automated path.

Editable original planning example
PlanAutomated kindsHoursE route
LimitedA,B,C,D4Existing manual route
Full shown scopeA,B,C,D,E12Included automated path
Mislabelled limited planClaims A–E at 4 hUnsupportedNo valid plan for E
Download editable CSV ↓

Work through the choice

A small release can be useful when its boundary and existing route are explicit. Removing E from automation does not remove E from business demand.

How much extra effort moves from the limited plan to the full shown scope?

Show the worked answer

8 hours: 12−4. Until then, E stays outside automation on the stated existing route.

Material to use in your plan

Use included case kinds, excluded kinds, their current route and effort to include each later. State the boundary in the release scope before estimating universal coverage.

Related resources