Milestone
A milestone is a named point in a project that has either been reached or has not, with no partial state. Unlike a task, it usually represents no work itself: it marks that a body of work is complete. Its value comes entirely from being unambiguous.
The binary nature is the whole design. Work in progress is reported in percentages, and percentages are where optimism accumulates. Something that is ninety per cent done has been ninety per cent done for two weeks in every project anyone has run.
A milestone refuses that. Reached, or not reached. It is the one honest signal in a status report.
The honesty survives only if the definition is testable. A milestone called integration complete invites debate at exactly the moment nobody wants one.
Spacing matters too. Milestones months apart give no early signal, and the first real news arrives too late to act on. Several weeks apart is usually the useful range: frequent enough that slippage shows while something can still be done about it.
Milestones on a client's side deserve the same treatment. Sign-off, content, access to a system: each is a point that is either reached or not, and each can stall a project as hard as anything the team does. Put them on the same list, with the same dates.
Where this shows up in PeopleMuster
PeopleMuster shows milestones reached against milestones planned on each project, beside the project's status and its health, tasks and setup scores.
Questions people ask
How is a milestone different from a task?
A task is work to be done. A milestone marks that a body of work is finished. Tasks have progress; milestones have only two states, which is what makes them useful.
How many milestones should a project have?
Enough that slippage shows early. A few weeks between them suits most projects. Too many and they behave like tasks; too few and the first warning arrives too late.
Should a milestone have a date?
Yes, and the date should move when reality moves. A milestone holding a date everybody knows is wrong trains people to ignore every date in the plan.