A PMO delivery gate for a civic payments portal asks what evidence shows readiness. Which set best reflects Domain 4 readiness determination?
Select an answer to reveal the explanation.
Short Explanation
Readiness isn’t a vibe check. Bring the RTM, Done backlog slice, acceptance signatures, and ops handoff—multiple receipts, one gate decision.
Full Explanation
A PMO delivery gate for a civic payments portal asking for readiness evidence is best answered with RTM coverage, committed backlog Done where used, acceptance sign-off, and ops handover readiness. That set reflects Domain 4 readiness determination across traceability, adaptive Done where applicable, acceptance, and operational transition. Civic payments demand multi-signal readiness, not a single vanity metric that ignores requirements evidence.
Team morale surveys alone without requirements evidence fail conceptually because morale is not requirements verification or acceptance. Vendor marketing slides without tests or acceptance sign-off fail because marketing is not delivery evidence for a payments portal. A single open defect count with no RTM or backlog view fails because a raw count without coverage context cannot show whether critical requirements are satisfied.
Exam caveat: Readiness determination combines coverage, Done/acceptance, and ops readiness—not morale, marketing, or isolated defect counts. Operational check: assemble a payments-portal readiness package with RTM coverage, Done status for committed scope, acceptance sign-off, and ops handover checklist; present it at the PMO gate; and treat missing elements as blockers.