Manual sections
POC, Pilot, MVP, V1
Defining the distinct purpose of each delivery phase.
Each stage exists for one core purpose. When that purpose is achieved, the stage ends.
1. POC (Proof of Concept)
Outcome: "Can this work at all?"
- Technical viability & integration feasibility
- Core architectural assumptions
- Critical blockers & performance constraints
Ends when: The team can answer YES or NO to feasibility. A POC is not a prototype, not a mini-MVP, and definitely not production code.
2. Pilot
Outcome: "Does this work in the real world?"
- Actual user interaction & data correctness
- Process alignment & supportability
- Failure modes in a controlled environment
Ends when: Behavior is confirmed. Pilot is where scope freeze becomes meaningful. It protects the experiment from uncontrolled variables.
3. MVP
Outcome: "Does this deliver the value promised?"
- Full-quality production readiness
- Smallest set of features to achieve outcome
- Measurable value (No extras)
Ends when: Core value is delivered. MVP proves the solution works. V1 proves the solution scales.
4. Version One (V1)
Outcome: "Is this ready for wide adoption?"
- Stability under realistic load
- Observability & incident handling pathways
- Documentation, training, and support runbooks
Ends when: The product is adoptable and not reliant on heroism. V1 is where the Shield activates fully.