Milestone
Defined checkpoint in a project timeline with a measurable outcome that makes progress visible, while taking up no duration itself.
A milestone marks an event of particular significance in a project, such as the completion of a planning phase, the sign-off of a prototype, or the commissioning of a system. Unlike a regular task duration, a milestone has no duration of its own; it is a point in time, not a span of time.
Milestones break a project into manageable sections and create fixed points where progress can be checked objectively. That makes them well suited as go or no-go decisions: the next phase only starts once a milestone has been reached.
For project control, milestones are especially valuable because deviations become visible early. If a milestone is missed, corrective action can still be taken before delays accumulate across the whole project and quietly push out the final delivery date.
Practical Example
A software project defines four milestones: requirements analysis complete in week 4, working prototype in week 10, test run complete in week 16, go-live in week 20. If milestone two slips by two weeks, the team immediately knows the final deadline is at risk.
How Leanshift Helps
Milestones create the honesty that continuous improvement needs: they show early where an initiative actually stands, instead of hiding problems until the very end.
Frequently Asked Questions
How many milestones should a project have?
There is no fixed number; one milestone per major phase is usually sensible, often between three and eight for mid-sized projects.
What happens when a milestone is missed?
The project team analyses the cause and decides whether resources need to be reallocated, the schedule adjusted, or the scope changed.