Project Kickoff Meeting Agenda
A project kickoff meeting is the first meeting of a project, where the team, the sponsor and key stakeholders agree on why the project exists, what it includes and who does what. This project kickoff meeting agenda runs 45 minutes and ends with a shared goal, a clear scope, an owner for each part and the first deadline.
Agenda
45 min · 7 parts
- 0:00Warm-up3 minIntroductions and a quick question to get everyone talking
- 3:00Why we're doing this5 minThe problem, the goal and how we'll measure success
- 8:00Scope10 minWhat's in, what's out and what isn't decided yet
- 18:00Roles8 minWho owns what, who decides and who needs to be kept informed
- 26:00Timeline9 minMilestones, fixed dates and the first deadline
- 35:00Risks5 minWhat could go wrong, and how we'll know early
- 40:00First steps5 minWhat happens tomorrow, and who does it
Free to start. Guests join from a link, no account needed.
- Length
- 45 min
- How often
- Once, after the project is approved and before the work starts, and again when a new phase begins or a new team joins.
- Who attends
- The project team, the sponsor or decision-maker and the stakeholders whose work or approval the project depends on.
- You leave with
- A shared goal, an agreed scope, an owner for each part of the work and the first deadline on everyone's calendar.
The agenda, part by part
How to run a project kickoff meeting
1. Warm-up
3 minAsk each person for their name, their role in the project and what they hope it achieves. If the team already knows each other, keep only the question. The point is that everyone speaks once, early.
Ask: What would make this project a success for you?
2. Why we're doing this
5 minThe sponsor explains the problem in plain words and why it matters now. State the goal as an outcome with a measure, such as fewer support tickets or a launch date, not as a list of features. Everyone should be able to repeat it after the meeting.
Ask: Six months from now, how will we know this was worth doing?
3. Scope
10 minList what the project will deliver and, just as important, what it won't. Writing down what's out of scope prevents many arguments later. Keep a third list for open questions, each with an owner and a date.
Ask: What might someone assume is included that isn't?
4. Roles
8 minName one owner for each workstream and say who makes which decisions: budget, scope changes, final approval. On larger projects, a simple RACI chart helps. Agree where questions go and how often stakeholders hear about progress.
Ask: When we disagree, who has the final say?
5. Timeline
9 minWalk through the main milestones and mark which dates are fixed and which can move. Spend most of the time on the first milestone: it should be close, concrete and small enough to hit. Agree how the team will track progress, for example with a weekly status meeting.
Ask: Which date can't move, and why?
6. Risks
5 minAsk everyone for the one thing most likely to derail the project. Keep the top two or three, name an early warning sign for each and give each one an owner who watches for it. Assumptions belong here too: anything you're counting on that isn't confirmed.
Ask: If this project fails, what's the most likely reason?
7. First steps
5 minClose with the first actions, each with one owner and a date in the next few days. Confirm when the team meets next and where the project documents will live. Send the notes the same day so the decisions stick.
Ask: What can each of us do before the end of this week?
Project kickoff questions to ask
- What problem are we solving, and for whom?
- What does success look like, and how will we measure it?
- What is out of scope?
- Who approves changes to scope, budget or dates?
- What are we assuming that we haven't confirmed?
- Which other teams or suppliers do we depend on?
- How, and how often, will we share progress?
- What's the first milestone, and when is it due?
Example: kicking off a website redesign
A marketing team kicks off a six-month website redesign with design, engineering and an outside agency.
Notes
- Goal: make it easier to book a demo; 30% more demo requests by September.
- Out of scope: the blog and the help center, planned for phase two.
- Roles: Chiara owns content, Daniel owns the build, Fatima (sponsor) approves the design.
- First milestone: approved sitemap and wireframes in three weeks.
- Risk: content from product teams arrives late. Warning sign: drafts not in by week two.
Action items
- Chiara: send the content request to each product team, by Friday.
- Daniel: set up the test site and share access with the agency, by next Wednesday.
Ways to adapt it
Client kickoff
Hold a short internal kickoff first to agree on scope and risks. Then use the same kickoff meeting agenda template with the client, adding a part on how you'll communicate and approve work.
Small internal project
Cut this project kickoff meeting template to 25 minutes: why, scope and first steps. A one-page brief sent beforehand covers the rest.
Large or cross-team project
Allow 90 minutes, send a project brief two days ahead and give more time to roles and risks, since that's where cross-team projects tend to get stuck.
Common mistakes
Presenting a finished plan instead of discussing it.
Instead: Send the brief beforehand and use the meeting for questions, the edges of the scope and risks. People commit to plans they helped shape.
Leaving the scope vague to avoid conflict.
Instead: Write down what's out of scope. A hard conversation now is cheaper than a missed deadline later.
Nobody knows who decides.
Instead: Name the decision-maker for scope, budget and dates before anyone leaves the room.
Ending without a first step.
Instead: Close with actions due this week, each with one owner. Early momentum sets the pace for the whole project.
Run it in Edworking
Your agenda keeps the meeting on time
Start a video meeting from any template. Edworking turns the agenda into the structure of the call, so nobody has to watch the clock.
Live agenda
A timer for every part
Everyone sees the agenda and how long is left in each part, with a clear moment when the meeting moves on.
AI notes
Notes that follow the agenda
AI takes the notes part by part and writes the summary and action items when the call ends.
Tabs in the call
Your work on screen, no sharing
Open docs, tasks and files as tabs in the call. Everyone sees the same thing without anyone sharing a screen.
Guests
Anyone can join from a link
Free to start. Clients, candidates and guests join from a link, with no account needed.
Frequently asked questions
45 to 60 minutes for most projects. Large or cross-team projects may need 90 minutes or a half-day workshop, and small internal projects can kick off in 25.
The project manager, the core team, the sponsor and anyone whose work or approval the project depends on. Keep it to people who will act on what's decided; everyone else can read the notes.
Introductions, the goal and why it matters, scope, roles and decision rights, the timeline, the main risks and the first steps. Send it a few days before, together with a short project brief.
An internal kickoff aligns your own team on scope, risks and who does what. A client kickoff aligns expectations with the client and covers how you'll communicate and approve work. Many teams hold the internal one first.
A one-page project brief: the problem, the goal, a draft scope, key dates and the people involved. It lets the meeting focus on questions and decisions instead of reading.
More meeting agenda templates
Project Status Meeting Agenda
Check progress against milestones, raise risks early and get the decisions the project needs.
5 parts
Decision-Making Meeting Agenda
Lay out the options, hear every concern and leave with a decision written down.
4 parts
Post-Mortem Meeting Agenda
Learn from a finished project or an incident, without blame, and leave with fixes that have owners.
5 parts