Who's in the room
- The full delivery team — engineers, designers, QA, anyone executing.
- The sponsor (briefly, at the start).
- Key stakeholders — at minimum the "manage closely" quadrant of your power-interest grid.
What gets covered
- Why this work — the business case, the outcome we're aiming at.
- Scope — in / out, with the explicit out-of-scope list.
- Roles — who's the PM, who's accountable for which deliverables (a high-level RACI).
- Schedule + milestones — high-level, not detailed.
- Risks + assumptions — the top 3–5 named risks, the major assumptions.
- Communication plan — standup cadence, weekly status, escalation path.
- Working agreements — definition of done, retro cadence, decision-making process.
↳ in the wild
The most useful slide in any kickoff is the one labeled "NOT IN SCOPE." Junior PMs leave it out because it's "negative"; senior PMs put it on a wall because it shortens every later argument.
What the team should leave with
A kickoff is successful when the team can answer three questions unprompted at the end: What are we building? Why does this matter? What are we explicitly NOT doing? If anyone hesitates on those, you have more aligning to do before you start.