Project Kickoff Checklist
Most projects that go sideways were set up wrong, not run wrong — unclear scope, a missing decision-maker, or a team that never agreed on what done means. This checklist walks the kickoff in order so everyone starts aligned. Work through it before you write a line of the plan, and see the rest of our work and onboarding checklists.
Curated by the Gisti team · Updated
Project Kickoff Checklist · 16 items
-
Define the project goal, scope, and success criteria
Write down what's explicitly out of scope, too — that's where scope creep starts.
-
Identify the stakeholders and, crucially, the single decision-maker
One clear owner of the final call prevents deadlock later.
-
Confirm the budget and the resources you actually have
-
Assemble the team and confirm each person's availability
-
Define roles and responsibilities so ownership is unambiguous
A simple RACI (who's responsible, accountable, consulted, informed) works well.
-
Gather and document the requirements
-
Break the work into milestones and a realistic timeline
-
Identify dependencies and risks, and note a mitigation for each
-
Choose your tools for tracking, docs, and communication
-
Set up the project workspace: the board, repo, or shared folder
-
Agree on a communication cadence and how status gets reported
-
Define what done looks like for the first milestone
-
Schedule the kickoff meeting and send an agenda in advance
-
Run the kickoff: align on goals, plan, roles, and next steps
Leave the room only when everyone can state the goal in one sentence.
-
Document the decisions made and share the notes with everyone
-
Confirm the first tasks and their owners before you close the kickoff
Make it yours in Gisti
Open this checklist in Gisti to tick items off, add your own, set reminders, and keep it in sync across Android and the web. AI can tailor every item to your exact situation.
Open GistiOpen this checklist in Gisti
Free to start · Works on Android & the web · Not affiliated with GitHub Gist.