Accelerator Phase Plan
Template for defining exit criteria for POC, Pilot, and MVP.
Purpose: Define objective success before work begins. Decide mathematically whether work may proceed to the next phase.
The Assembler (Macro Gantt)
In the Governance OS, Phase Plans are not static spreadsheets. They are built interactively in the Assembler and rendered on the Macro Gantt timeline. Every phase requires explicit boundaries.
Phase Success Criteria
At the entry of any phase, the following must be logged in the Lens:
- ☐Phase Hypothesis (What are we proving?)
- ☐Observable Success Signals
- ☐Explicit Failure Signals
Failure Mode: Without criteria, phases drift and never end.
Gate Checkpoints
At the exit of every Accelerator phase, a Gate milestone must exist on the timeline:
- ☐Validate each Success Signal as Pass/Fail.
- ☐Verify all Dependencies have resolved.
- ☐Obtain Cryptographic Sign-Off from the Delivery Owner.
Failure Mode: Skipping gates smuggles technical debt into production.
Executing a Phase Transition
When a phase ends (e.g., Pilot concludes), the transition to the next phase (MVP) is not automatic. The Delivery Owner must trigger a Change Forum/Gate Review.
- Review the Evidence: Do the links in the DoD match the Success Signals?
- Check the Trade-Off Log: Did scope shift during the phase?
- Decision: Proceed / Stay (Extend Phase) / Reduce Scope / Terminate.
- Lock: Apply the cryptographic signature to update the OS status.