How many milestones should a project have?

The right number depends on project size and duration. A rule of thumb is one milestone per month of project duration, or one per major phase. A 3-month project might have 4-6 milestones. A 12-month project might have 10-15. Too few milestones provide insufficient visibility; too many create noise without meaningful signal.

What happens when a milestone is missed?

A missed milestone should trigger an impact assessment (how does this affect the overall timeline?), root cause analysis (why was it missed?), recovery planning (can the delay be recovered?), stakeholder communication, and a decision about whether to adjust the plan, add resources, or reduce scope. Missed milestones are early warnings that should not be ignored.

Are milestones used in Agile projects?

While Agile focuses on continuous delivery rather than milestone-driven progress, milestones remain valuable for stakeholder communication, release planning, and alignment with external dependencies. Many Agile teams use milestones at the roadmap level while using sprints and velocity for day-to-day tracking.

Book Free Assessment Calculator

Milestone

Also known as:project markercheckpointphase gate

A significant point or event in a project that marks the completion of a major phase, deliverable, or achievement, used to track overall project progress.

In-Depth Explanation

A milestone is a marker in a project schedule that signifies an important achievement or decision point. Unlike tasks, milestones have zero duration - they represent a point in time when something significant is completed or decided.

Types of milestones:

Project milestones: Major project phases (requirements complete, design approved, go-live)
Contractual milestones: Deliverables tied to payment or contractual obligations
Governance milestones: Stage gates requiring approval to proceed
External milestones: Deadlines imposed by regulators, customers, or events
Internal milestones: Team-set targets for tracking progress

Characteristics of good milestones:

Specific: Clearly defined and unambiguous
Measurable: It is clear when the milestone is achieved
Significant: Represents meaningful progress, not trivial checkpoints
Time-bound: Has a target date
Achievable: Realistic within the project constraints

Milestone management practices:

Define milestones during project planning
Link milestones to specific deliverables or decisions
Set target dates based on critical path analysis
Track milestone status regularly (on track, at risk, missed)
Report milestone progress to stakeholders
Use milestone slippage as an early warning of project delays
Celebrate milestone achievements to maintain team morale

Common project milestones:

Project charter approved
Requirements signed off
Design phase complete
Development complete (code freeze)
User acceptance testing complete
Go-live / launch
Post-implementation review complete
Project closure

Business Context

Milestones provide clear progress markers for stakeholders, enable early detection of schedule slippage, and serve as natural points for project reviews and go/no-go decisions.

How Clever Ops Uses This

Clever Ops defines clear milestones for all client projects, providing Australian businesses with transparent progress markers and natural review points. We use milestone tracking to ensure projects stay on course and stakeholders have visibility of progress.

Example Use Case

"A project plan includes 8 milestones across 6 months, with the steering committee reviewing progress at each milestone and providing approval to proceed to the next phase."