Project Kickoff Meeting Agenda and Checklist

A project kickoff meeting agenda for a small team fits in 45 to 60 minutes and settles four questions: what the goal is, what is in scope and what is out, how decisions get made, and where the work is tracked. Open with why the project exists, spend most of the time on scope, name one person who decides, and close by writing the first tasks and the first decisions down before anyone leaves. Invite only the people who will do the work, the person who asked for it, and whoever must approve the result. The timed agenda, a checklist for before and after, and a client version are below.

Who attends

Keep the room small enough that everyone speaks. Atlassian’s project kickoff play↗ (opens in a new tab) lists the roles worth having: a sponsor, the most senior stakeholder with the most to gain or lose; a project leader, who sets the vision on what the team is delivering and why; a facilitator who keeps the meeting flowing and focused; the core team who do the work; and stakeholders with a stake in the outcome. For a small team that usually collapses to:

• The person who asked for the project, for the first ten minutes at least. They explain why it matters, and they are the one who can say “that is out of scope” with authority.
• The lead, who runs the meeting and owns the result.
• Everyone who will do the work, including anyone part-time. Someone who hears the scope second-hand will build the second-hand version.
• Anyone who must approve the result, if that is not the person who asked. Finding a hidden approver in week five is the most expensive surprise a project can have.

If an AI assistant will do some of the work, it does not attend, but it does need what the meeting produces. Plan to write the outcome down where the assistant will read it; the last section covers how.

The four questions a kickoff must settle

1. Goal: what will be true when the project succeeds, and how you will check it. Write it as an outcome, not an activity: “Customers can book online without calling,” not “Build a booking page.” If the person who asked describes success differently from the team, that is the most useful thing the meeting can discover.
2. Scope in and out: what the project delivers, and just as carefully, what it does not. The “out” list prevents more arguments than any other part of the meeting, because it is where people find out they assumed different things.
3. How decisions get made: who decides, and who only advises. Atlassian’s DACI framework↗ (opens in a new tab) names an Approver, “the one person (yes: one!) who makes the decision,” separate from the contributors who have “a voice, but not a vote.” For a small team the whole framework can be one sentence in the meeting: “Priya decides scope; anyone can raise a concern.”
4. How work is tracked: where tasks live, how often the team looks at them, and who writes the update for the person who asked. Agree it now, or each person will track the project in a different place by Friday.

The single decider matters more than any other line on the agenda. The US Digital Service’s Digital Services Playbook↗ (opens in a new tab) has a play for it, “Assign one leader and hold that person accountable,” and says there must be a single product owner with the authority to make business, product and technical decisions. A project where two people can each say yes has, in practice, nobody who can say no.

A timed agenda for 45 to 60 minutes

Atlassian’s full kickoff play runs 90 minutes and includes breakout groups, which suits a larger team. A small team can cover the same ground in an hour:

Project kickoff: [Project name]
[Month day, year], [time], [room or link]
Lead: [name]   Decides: [name]   Notes: [name]

 5 min  Why this project, from the person who asked
 5 min  The goal, and how we will check it
15 min  Scope: what is in, what is out
10 min  How decisions get made, and who decides what
10 min  How work is tracked, and the first tasks
10 min  Risks and questions: what could make this late or wrong
 5 min  Read back: decisions made, tasks created, next check-in

For 45 minutes, cut the risks section to five minutes and hold the scope discussion to ten. Do not cut the read-back. The last five minutes, where the note-taker reads out every decision and every task with its owner, is what turns a good conversation into an agreement.

Kickoff meeting checklist

Before
- [ ] Draft the goal in one or two sentences and send it with the invite
- [ ] List everything anyone has asked for, to sort into in and out
- [ ] Confirm who decides, and that they are coming
- [ ] Choose the note-taker
- [ ] Set up the board or tracker the tasks will go on

During
- [ ] Goal agreed, with a way to check it
- [ ] Scope in and scope out written down
- [ ] One decider named for scope and priorities
- [ ] First tasks written, each with one owner
- [ ] Next check-in booked

After (same day)
- [ ] Send the notes: decisions, tasks, open questions
- [ ] Record the decisions where the team and its AI assistants read them
- [ ] Put the first tasks on the board
- [ ] Write the one-page plan, if the project needs one

The notes themselves follow the same shape as any meeting’s; the meeting minutes template covers how to write them with decisions and action items. The one-page plan that follows a kickoff is the project plan template. This agenda deliberately stops short of both, and of a formal charter: its job is agreement, not documentation.

A client kickoff meeting agenda

A client kickoff settles the same four questions with two differences: the client decides the goal and the scope, and the team decides how the work is done. Adjust the agenda to make that line visible:

• Start with the client’s own words on why they hired you, and write the goal back to them in the meeting. A goal they recognize as theirs is one they will defend when scope pressure arrives.
• Spend longer on scope out. Clients rarely mind hearing what is excluded in the first meeting; they mind very much hearing it in the fifth.
• Name the decider on each side: who at the client approves the work, and who on your team the client should talk to. Two names, written down.
• Agree what the client owes you and when: content, logins, feedback. List each as a task with the client as the owner, because client dependencies are the most common reason agency projects stall.
• Agree how the client will see progress, and how often they will get an update, so “where are we?” is answered before it is asked.

Leaving with the first board and the first decisions

The best kickoffs end with the work already visible. On a fenbs board, the note-taker can do it before the meeting ends. The tasks from the read-back go in with Add many: paste them as a list, set the project once for the whole batch, start any line with bug:, feature: or enhancement: to set its kind, and check the preview before anything is created. fenbs has no assignee field you can set, so an indented line under each task, such as “Owner: Tom,” becomes that task’s note and says whose it is.

- [ ] Agree the three services and their prices for online booking
      Owner: Priya. Decided at kickoff: custom quotes stay on the phone.
- [ ] Apply for the payment provider account
      Owner: Tom. Risk raised at kickoff: approval can be slow.
- [ ] Client to send the service descriptions
      Owner: the client contact.

The decisions go on the Decisions and rules page. A decision records what was chosen and who decided, and the decider is always a person. A decision that should hold from now on, such as “custom quotes stay on the phone,” can be marked as a rule, and every connected AI assistant reads the rules first, in full, before it touches the board. That is how an assistant that was never in the meeting still respects what the meeting agreed. For how to choose and record decisions in general, see the decision making framework.

For a client kickoff, add the client to the board with the Client role: they see the board and can comment, and cannot change anything. If they should add their own requests, the Reporter role lets them add tasks and edit only their own. The client project board template starts with a kickoff task already in Completed. fenbs has no due dates, so milestone dates stay in the plan, not on the board.