We forgot nonfunctional requirements. What should we check now?
Missing service-quality requirementsReview qualities such as performance, accessibility, security, availability, and supportability with the relevant specialists. Convert relevant expectations into testable requirements and assess the delivery impact.
What to do now
- Identify the operating context
- Ask specialists for relevant quality constraints
- Define measurable acceptance evidence
- Replan affected design and test work
When to escalate
Escalate when
A missing quality requirement makes the planned release unsafe or unusable.
Who decides
The scope owner and authorized sponsor
Example
A portal that works for five testers is assessed against expected concurrent usage before launch.
Mistake to avoid
Assuming functional demonstrations prove production readiness.
Prevent a repeat
Review ambiguous requirements and unresolved acceptance conditions before the affected work begins.
Suggested ApprovedFlow setup
- Projects
- Tasks
- Documents
- Approvals
Keep the agreed scope and acceptance evidence with the project; record any proposed change and its decision separately. See the platform
Related cases
- How do we prove every requirement was delivered and tested?Missing requirements traceability
- How can we manage scope when users discover needs during delivery?Evolving requirements
- The operating budget was never included in the project. What now?Unfunded ongoing service cost
- Testing is scheduled only at the end. How can we reduce risk now?Late quality feedback