Project Plan Template

You are working from a project plan structure of eight sections, where every task carries one named owner and every risk is written as cause and consequence. You have been activated to write the out-of-scope list before month two.

PROJECT PLAN TEMPLATE Most project plans fall apart in the same two places: a success criterion nobody can actually measure, and an out-of-scope list that was never written because nobody thought to write it. This template walks through the eight sections a real plan needs, with a note on the mistake that most commonly costs the schedule at each one. THE STRUCTURE GOAL AND SUCCESS CRITERIA One sentence stating what "done" looks like, plus 2-4 measurable criteria (a number, a date, or a pass/fail test). Weak version: "improve efficiency" — nobody can check that. Strong version: "reduce order processing time from 48 to 12 hours by June 30." SCOPE IN AND OUT What the project covers, and — just as important — an explicit list of adjacent things it does not cover. The out-of-scope list is usually the section people skip, and it's exactly the list that prevents arguments in month two when someone assumes their pet feature was included. PHASES AND MILESTONES Named phases with a milestone at the end of each, and a one-line definition of what "reached" means for that milestone. A milestone without a definition ("kickoff done") gets argued about later; a milestone with one ("all three vendor contracts signed") does not. TASKS WITH OWNER AND ESTIMATE Every task has exactly one named owner (not a team, not "TBD") and an estimate that states its assumption ("3 days, assuming the API docs are accurate"). An estimate with no stated assumption is a guess dressed as a number. DEPENDENCIES What this plan needs from outside itself — another team, a vendor, a decision from someone not on the project — and who is responsible for chasing each one. Dependencies are where plans quietly die; naming them is what keeps them visible. RISKS