G1 · Commit

Can we commit to scope, price and approach?

Source
Stage-Gate®; PRINCE2® stage boundaries; ISO 21502 governance
Level
B · established practice

Evidence

Solution outlinecriticalany context
Estimate (range)criticalany context
Assumptions and exclusions logcriticaldepends on context
Assumptions and exclusions logrequiredwaivabledepends on context
Proposalcriticaldepends on context
Contract / statement of workcriticaldepends on context
Business casecriticaldepends on context
Paid discovery reportcriticaldepends on context
Success metrics with baselinescriticaldepends on context
Success metrics with baselinesrequiredwaivabledepends on context
Success metrics with baselinesoptionaldepends on context
Risk register (RAID)criticaldepends on context
Risk register (RAID)requiredwaivabledepends on context
Risk register (RAID)optionalany context

Checks

  • Delivery approach chosen and recorded
  • Contract model fits the uncertainty: fixed price only for clear or complicated scope, or after a paid discovery
  • Regulatory obligations listed in the SOW assumptions and priced
  • Service levels agreed in the SOW: hours, priorities, response and resolution times

How the gate runs

Predictive
Phase gate: held once, at the end of the stage.
Agile (iterative)
Rolling gate: held per release; item readiness via Definition of Ready, completion via Definition of Done.
Flow (Kanban)
Policy gate: explicit exit policies on the board columns, applied to every item.
Hybrid
Phase gate per phase, with iterations or flow inside the phase.
For agents · MCP
explain_node({ "id": "g.g1" })