Meeting Prep Pro

Project Launch Review — Meeting Brief

Length: 45 minutes.

Participants: product owner (decision owner), engineering lead, support lead.

Goal: decide whether Friday launch remains appropriate while two of five acceptance tests are incomplete.

Known and unknown

• Two acceptance tests are incomplete; owners expect results Wednesday.
• The severity and consequences of the incomplete tests are unknown.
• Rollback readiness and support coverage need confirmation.

Pre-read requests

• Test status, expected completion date, pass criteria, and impact if a test fails.
• Engineering’s rollback plan, dependencies, and recovery owner.
• Support coverage plan and escalation contact for launch day.
• Product’s launch criteria and any external commitments tied to Friday.

45-minute agenda

1. 0–5 min — Goal and decision rule: confirm who decides and what evidence is required.
2. 5–15 min — Test status: review the two incomplete tests and risk of each outcome.
3. 15–25 min — Readiness: confirm rollback, monitoring, dependencies, and support coverage.

25–35 min — Options: launch Friday, delay, or use a staged/limited release if feasible. Compare impact and reversibility.
5. 35–42 min — Decision: record decision, rationale, assumptions, and dissent.
6. 42–45 min — Owners: assign remaining checks, deadlines, and communication owner.

Decision questions

• What user or operational impact would each incomplete test reveal?
• What criteria must pass before release, and who confirms them?
• Can rollback be tested and support staffed by Friday?
• What is the latest responsible decision time, and who communicates a delay?

Materials: test report, release criteria, rollback checklist, support rota, and launch communication plan. No launch recommendation is made without the missing risk evidence.