Go/no-go meeting
Also called: go/no-go decision, release decision meeting, ship/wait call
A go/no-go meeting is where the people accountable for a release decide, from the evidence in front of them, whether it ships or waits.
A go/no-go meeting is the point where a release is approved or held. The people in the room should be the ones who can accept risk: Product for the user and the business, Engineering for the system, and whoever owns operations and support.
The meeting fails when every indicator is green and the risks sit in footnotes. Pass rates without journey names, an environment that does not resemble production and deferred defects without owners all let a room nod a release through without deciding anything.
I prepare it with a readiness note sent in advance, so the meeting is spent on the open items and not on reading slides aloud. A good go/no-go is slightly uncomfortable, because it names what is not known.
Template: Release readiness note template