scope & shape — volume III
Introduction
Volume II ended with a Feature Brief signed off — a witnessed problem, a prediction, a check date. Volume IV will begin with the first commit. This volume is the work of bridging those two — turning a prediction into the shape of a release.
Scope is not a list of tasks. Scope is the act of declaring, in writing, what changes in the world this cycle and what does not. A scope without a not statement is not a scope; it is a backlog.
Scope is the smallest end-to-end slice of work that — when shipped — will move the prediction. Anything larger is a backlog. Anything smaller is a task.
What this volume covers
Nine parts.
- Epic Naming & Kickoff — coherent activities, named after what the person does.
- Story Mapping — Epics as columns, stories as rows, releases as slices.
- Walking Skeleton — the smallest end-to-end release that changes the situation.
- Story Writing — person, moment, done, out-of-scope, Gherkin-ready.
- Amigos & Gherkin — the trio session that produces shared meaning.
- Architecture Decision Records (ADR) — constrained choices with rejected options.
- Sequence, Schema, API — the three technical drawings every Epic needs.
- Ilities Selection — which non-functional requirements matter, to what level.
- Slicing & Prioritization — which stories in which release, value-driven.
Volume III is where the chain feels most operational. It is also where the most chain damage is done — by skipping amigos, by writing stories without journey references, by choosing technical options without writing ADRs. Most production bugs trace not to Execution but to Scope: the missing state, the unwritten edge case, the technical choice that was made in a Slack thread.