Product
Decide what to build first, and what to leave out.
From every request to a first version
Diagram: eighty-three requested features. Ranked by value, most fade. Five remain as version one, connected in the order they must be built.
A field of possible features narrows to the few that prove the product, ordered by dependency.
Stages
1 of 5
What are people actually asking for, and why?
What you get
One list, not five
What we do
What we do
Definition
The user, the problem and the smallest version that proves it.
Prototypes
Working versions users react to before the full build.
Roadmap
Ordered by dependency, with trade-offs written down.
Delivery
Acceptance criteria and release plans.
Works with
Start with the objective.
Usually a sprint, or embedded through the build.