Skip to content

G4 · Requirements ready

Is the next work specified well enough to design and build?

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

Evidence

To-be process modelcriticaldepends on context

Requirements specificationcriticaldepends on context

Product Backlogcriticaldepends on context

Acceptance criteriacriticalany context

Mockups / wireframescriticalwaivabledepends on context

Prototypecriticaldepends on context

Mockups / wireframesoptionaldepends on context

Non-functional requirementscriticaldepends on context

Non-functional requirementsrequiredwaivabledepends on context

To-be process modelcriticalwaivabledepends on context

To-be process modelrequiredwaivabledepends on context

Fit-gap logcriticaldepends on context

Fit-gap logrequiredwaivabledepends on context

Data flow modelrequiredwaivabledepends on context

Data mappingrequiredwaivabledepends on context

Data flow modeloptionaldepends on context

Use case specificationsoptionaldepends on context

Requirements traceability matrixcriticaldepends on context

Requirements traceability matrixrequiredwaivabledepends on context

Requirements traceability matrixrequiredwaivabledepends on context

Compliance requirements registerrequiredwaivabledepends on context

Definition of Ready (agreed text)optionaldepends on context

Checks

Priorities agreed with the decision-maker
Every requirement traced to a goal

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