Privacy requirements for a resident services portal appear in workshops but are missing from the RTM with no linked tests. What is the readiness implication?
Select an answer to reveal the explanation.
Short Explanation
If privacy never made it into the RTM or tests, you don’t have a boarding pass—you have sticky notes. Gaps in traceability mean you’re not ready to claim delivery.
Full Explanation
Privacy requirements for a resident services portal that appear in workshops but are missing from the RTM with no linked tests mean the product is not ready—incomplete RTM coverage for privacy requirements means readiness cannot be claimed. Workshop discussion without traceability and verification is awareness, not evidence. Civic portals handling resident data need privacy requirements traced and tested before go-live claims that expose the city to avoidable risk.
Calling the portal ready because workshop notes alone prove delivery readiness fails conceptually because notes are elicitation records, not verification evidence. Calling it ready because privacy is never traced in municipal projects fails because privacy commonly requires explicit tracing and controls in public-sector systems. Calling it ready if the homepage loads within five seconds fails because homepage performance does not prove privacy requirement coverage or test completion.
Exam caveat: Readiness requires traced and tested coverage of critical requirements such as privacy, not workshop memory or unrelated metrics. Operational check: add privacy requirements to the RTM, define and execute tests, remediate gaps, and only then present resident-portal readiness with privacy coverage evidence at the delivery gate.