How do you use milestones and dependencies to avoid delays?

Most delays are not a surprise; they are a task that quietly waited for another one. Milestones show the dates that matter, and dependencies show what has to finish first.

Short answer

A milestone is a checkpoint with a date, such as “design approved”.
A finish-to-start dependency means task B cannot begin until task A has finished.
Link only the dependencies that are real, otherwise the picture becomes noise.
Review upcoming milestones weekly and ask what could slip.
When a task runs late, check which tasks and milestones depend on it.

Choosing milestones

Pick points that mean something to the client or the team, such as approval or launch.
Keep to three to six per project so they stay meaningful.
Each milestone should have a clear definition of done.

Setting up dependencies, step by step

List the tasks needed to reach the milestone.
For each task, ask what must be finished before it can start.
Link those tasks finish-to-start.
Give every task an owner and a deadline.
Check the longest chain of linked tasks: it sets your earliest finish.
Review it each week and move deadlines by hand when something slips.

Common mistakes

Linking everything to everything.
Setting milestones with no date.
Expecting dates to move by themselves when a task runs late. They are your decision.

Example: a shop refit

A refit has the milestone “shop opens on 1 June”. Painting cannot start until the electrics are finished, and shelving cannot start until the painting is dry. When the electrician is two days late, the chain shows both later tasks are affected, so the owner moves them and tells the shop manager early.

Example: a website launch

A launch has three linked stages: design takes 5 working days, the build takes 8 and testing takes 3. Started on day 1, design ends on day 5, the build on day 13 and testing on day 16. If design slips by 2 days, the whole chain moves and launch lands on day 18, unless the owner decides to shorten the build.

Questions people ask

How many dependencies are too many? If you cannot explain a link in one sentence, remove it.

Can a task have more than one dependency? Yes. It can start only once every task it depends on has finished.

Who moves the dates? The task owner or project lead, by hand, after talking to the people affected.

More mistakes to avoid

Treating a milestone as a task. It is a checkpoint, not work in itself.
Forgetting to tell the client when a milestone moves, so the surprise arrives on the day.
Reviewing the chain only at the end of the project, when nothing can be changed.

How 4myprojects helps

Milestones per project and finish-to-start dependencies between tasks, stored as dates.
Dates are not rescheduled automatically; the owner decides what moves.
A chronological list of sprints, milestones and deadlines.
Health and risk indicators calculated from rules, such as overdue tasks.