G6 · Test readiness

Is the solution complete enough to verify end to end?

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

Evidence

Incrementcriticalany context
Test casescriticaldepends on context
Automated test suitecriticaldepends on context
Test reportcriticaldepends on context
Test reportrequiredwaivabledepends on context
Test reportcriticaldepends on context
Defect logoptionalany context
Technical debt register / known restrictionsrequiredwaivabledepends on context
Release notesoptionaldepends on context
User and admin documentationoptionaldepends on context
Trial load reportrequiredwaivabledepends on context
Assumptions and exclusions logrequiredwaivabledepends on context

Checks

  • 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

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.g6" })