Run a gate

Pick a gate and a project, set the state of each piece of evidence, and get the outcome, the rule that fired and the questions to ask. This is the check_gate answer.

Evidence · 9

Mark all:
Cutover plan / runbookcritical
Cutover plan / runbook
Rollback plancritical
Rollback plan
Migration and reconciliation reportcritical
Migration and reconciliation report
Training materialscritical
Training materials
Support model and SLAcritical
Support model and SLA
Release notesrequired
Release notes
Operational readiness report (OAT)required
Operational readiness report (OAT)
Business readiness assessmentrequired
Business readiness assessment
Communication planrequired
Communication plan
GoR5Verdict ↓

G8 · Go / no-go

Is it safe to switch to the new solution now?

GoR5

Proceed to the next stage and record the decision.

Go: all required evidence is present, current, or waived with a reason and an approver.

All gates

G0 · Bid / no-bidShould we pursue this opportunity at all?
  • Uncertainty assessed (complexity domain named)
  • Client decision-maker identified
  • Sponsor and funding source identified
  • Fits our capabilities and strategy

The evidence set depends on the project context. Gate details

G1 · CommitCan we commit to scope, price and approach?
  • 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

The evidence set depends on the project context. Gate details

G2 · LaunchIs everyone ready to start work?
  • Client decision-maker available for the agreed cadence
  • Business decision-maker available for the agreed cadence
  • Charter filled in together with the client, not after the fact
  • Charter agreed with the business decision-maker and the sponsor, not after the fact
  • Tools and environments ready
  • One accountable lead with decision rights named

The evidence set depends on the project context. Gate details

G3 · Scope baselineDo we understand the needs well enough to specify them?
  • Needs confirmed with the people who have them
  • Conflicting needs made visible and owned

The evidence set depends on the project context. Gate details

G4 · Requirements readyIs the next work specified well enough to design and build?
  • Priorities agreed with the decision-maker
  • Every requirement traced to a goal

The evidence set depends on the project context. Gate details

G5 · Design and plan approvedCan the team build without guessing, and do we know when it will arrive?
  • Top risks have owners and responses
  • Forecast stated as a range, not a single date
  • Critical path meets the fixed date with an explicit buffer; the fallback decision date is set
  • Forecast at the agreed confidence meets the fixed date; fallback scope agreed

The evidence set depends on the project context. Gate details

G6 · Test readinessIs the solution complete enough to verify end to end?
  • Every increment meets the Definition of Done
  • Deliverables reviewed against the agreed quality criteria
  • Code reviewed and the pipeline green
  • Configuration deployed to test from the packaged solution; no manual changes in test

The evidence set depends on the project context. Gate details

G7 · AcceptanceDoes the solution do what the business needs?
  • No open critical defects
  • Acceptance criteria verified by business users
  • Verified end to end by the owners of consuming systems

The evidence set depends on the project context. Gate details

G8 · Go / no-goIs it safe to switch to the new solution now?
  • Rehearsal done when data is migrated
  • Rollback rehearsed on a copy of production and timed
  • Business ready: people trained
  • Cut-off agreed with users and counterpart systems
  • Counterpart systems confirmed readiness and the window
  • Non-functional requirements verified: performance and security results against the NFR
  • Migration report is from the final rehearsal or the production load, not from a trial load
  • Users set up, licences assigned, roles tested with real accounts

The evidence set depends on the project context. Gate details

G9 · HandoverIs the solution stable enough for operations to own it?
  • Incident rate back to the agreed baseline
  • Support team accepts ownership
  • Adoption at the agreed level (active users; work is done in the new system or process, not around it), measured against the success metrics
  • Warranty start and defect handling recorded

The evidence set depends on the project context. Gate details

G10 · ClosureIs everything closed and was the value delivered?
  • Contracts, budget and access closed
  • Success metrics compared with their baselines, or a benefits review scheduled
  • Pivot, persevere, scale or stop decided against the success metrics

The evidence set depends on the project context. Gate details