Milestone vs deliverable

A deliverable is something a project produces and hands over, such as a document, a working feature or a finished room, and a milestone is a point in the schedule, with no duration, that marks something reached, often the acceptance of a deliverable.

Updated .

The rule

A deliverable is the output of work. It has a size, an owner and a test that says when it is accepted, and tasks with durations produce it. A milestone is a date the plan watches. It takes no time and has no work of its own: it is reached when the work before it is done.

The two usually come in pairs, with a task between them. The deliverable is the thing ("the requirements document"), the task is the work ("write the requirements document"), and the milestone is the event ("requirements approved"). In a schedule the milestone is a task of zero duration linked after the work, so it moves when the work moves.

Not every deliverable needs a milestone, and not every milestone has a deliverable: a contract signed or a permit issued is a milestone with nothing of the project's own to hand over.

Deliverable: produced by tasks with a duration, accepted against a test. Milestone: duration 0, reached when the work before it finishes.

Worked example

The Software Product Launch plan from the free project plan templates: 12 tasks in 3 phases (Discovery, Build and Launch) and two milestones. Three of its deliverables and both milestones, with the work behind each.

Deliverables and milestones in the Software Product Launch plan
ItemKindDays of workWhere it comes from
Product requirements documentDeliverable5The task "Write product requirements doc", in Discovery
MVP, backend and frontendDeliverable36Two build tasks of 18 days each, in Build
Launch announcement and press kitDeliverable6The task "Draft launch announcement + press kit", in Launch
Beta releaseMilestone0Day 44 of the plan: the beta opens to customers
General availabilityMilestone0Day 58 of the plan: the product is on general sale

The deliverables have days of work behind them and someone who accepts them. The milestones take no time and are the two dates a launch review asks about. Mark the 18-day frontend build as a milestone too, and the list of dates grows a task that takes three and a half weeks, while the review loses sight of the two dates that matter.

What goes wrong in practice

  • Milestone inflation: every task marked as a milestone, so the milestone list has forty rows and no signal.
  • Milestones with a duration. A milestone that takes days is a task, and its finish is the date that was meant.
  • Milestones typed in on a fixed date with no link to the work, so they stay on time while the work behind them slips.
  • A deliverable with no acceptance test, so it is never clearly done and the milestone after it is never clearly reached.
  • Paying against a milestone that is reached by a date on the calendar rather than by an accepted deliverable.

See this in your own file

Pick one of the free project plans, see its phases, tasks and milestones on the page, and download it as a spreadsheet for Excel or Google Sheets.

See the milestones in a ready project plan

Longer read: Milestone vs Deliverable vs Task: The Real Difference

Questions

Is a milestone a deliverable?

No. A deliverable is something the project produces; a milestone is a moment the plan marks, often the moment a deliverable is accepted. "Design signed off" is a milestone, and the signed-off design is the deliverable.

Can a milestone have a duration?

In a schedule, no: a milestone is a task of zero duration. Microsoft Project treats a task with zero duration as a milestone and draws it as a diamond on the Gantt chart.