Handbook
MVP plan — {name}
Template
Template — Copy this file into your project and fill in the sections. Do not edit the blueprint original.
MVP plan —
Core value proposition
Target users
Scope boundaries
Must have (MVP scope)
| Ingot |
Value |
Acceptance criteria |
|
|
|
Should have (first phase after MVP)
Won't have (explicitly deferred)
Forge iterations
| Iteration |
Focus |
Key Ingots |
| F{n} |
|
|
Assay Gate criteria (MVP exit)
- [ ] All "must have" Ingots completed and reviewed
- [ ] Core user journey works end-to-end
- [ ] Tests pass (unit, integration; E2E for critical paths)
- [ ] Performance acceptable for target user volume
- [ ] Security review completed (Security Versona)
- [ ] Onboarding / documentation sufficient for target users
- [ ] Rollback plan in place
- [ ] Monitoring and alerting configured
Versona sessions planned
| Discipline |
Timing |
Focus |
| BA |
Refinement |
Are "must have" items correct and complete? |
| UX |
Design |
Is the core journey usable without training? |
| Testing |
Pre-release |
Is test coverage adequate for core paths? |
| Security |
Pre-release |
Are auth, data protection, and input validation sound? |
Risks
| Risk |
Likelihood |
Impact |
Mitigation |
|
|
|
|
Success metrics (post-launch)