The go or no-go judgement.
WHAT THE DECISION REQUIRES
What has been tested, and what has not Known defects, and their severity Risk areas remaining uncertain Whether rollback is possible
WHO MAKES IT
The business, informed by testing.
WHAT TESTING PROVIDES
Information, not permission.
WHAT TO PRESENT
Coverage of the important areas Open defects by severity What was not tested, and why The recommendation, with reasoning
WHAT EXIT CRITERIA ARE
Agreed conditions for release.
WHAT THEY MIGHT INCLUDE
No open critical or high defects Critical paths verified Performance within target Security findings addressed
WHY AGREEING THEM IN ADVANCE MATTERS
Deciding under release pressure produces different answers.
WHAT TO DO WHEN THEY ARE NOT MET
State it plainly, and let the business decide with that knowledge.
WHAT TO RECORD
The decision, and what it was based on.
WHY
It is examined after an incident.
WHAT REDUCES THE WEIGHT OF THE DECISION
The ability to release frequently, and to reverse quickly.
WHY
Small reversible releases make each decision smaller.
WHAT TO ARGUE FOR
That capability, above more testing.
