BRÈCHE
MVP scope worksheet
Guide: /guides/mvp-scope
Updated: 2026-09-25

Write the smallest complete release, the assumptions behind it and the evidence that would justify the next one.
Fill this in locally. Nothing is sent to BRÈCHE.
Do not include passwords, API keys, wallet recovery phrases or private customer data.

1. Audience and current workaround
Describe one user group, its current workflow and the specific problem with that workflow.
Your notes:


2. Assumption to test
Write an observable claim about how this group would use or pay for the product. Say what evidence could contradict it.
Your notes:


3. Complete user flow
List entry, permission check, main action, saved result and the way the user returns to it.
Your notes:


4. Required failure handling
Cover invalid input, lost access, repeated actions and unavailable dependencies. Write the recovery or explanation the user needs.
Your notes:


5. Launch, manual, later
Place each requirement in one of these groups. A manual step needs an operator, instructions and a capacity limit.
Your notes:


6. Entitlements and billing
Define who can use the product and when access changes. State whether the first release needs online billing and why.
Your notes:


7. Dependencies and unresolved decisions
Name external systems, content and approvals. Record an owner and a resolution step for each unknown.
Your notes:


8. Review after real usage
Decide when to review completed tasks, points of failure, operator work and returning users. State what would change the next release.
Your notes: