Dependency types (FS, SS, FF, SF), leads and lags
A dependency is a link between two tasks that says which end of the first task (the predecessor) controls which end of the second (the successor): finish to start, start to start, finish to finish or start to finish.
Updated .
The rule
Finish to start (FS): the successor starts once the predecessor finishes. Start to start (SS): the successor starts once the predecessor starts. Finish to finish (FF): the successor finishes once the predecessor finishes. Start to finish (SF): the successor finishes once the predecessor starts.
A lag is a wait added to the link, counted in working days unless it is set as elapsed time. A lead is a negative lag: it lets the successor begin before the link would otherwise allow, so the two tasks overlap.
Each link sets the earliest date allowed, not a fixed date. When a task has several predecessors, the one that gives the latest date wins.
FS: successor start >= predecessor finish + lag. SS: successor start >= predecessor start + lag. FF: successor finish >= predecessor finish + lag. SF: successor finish >= predecessor start + lag.Worked example
The predecessor is "Build the frame", 10 working days, on days 11 to 20. The successor is "Install the windows", 4 working days. Days are working days, each counted whole, so a task on days 11 to 20 starts on the morning of day 11 and finishes at the end of day 20.
| Link | What it says | Install the windows |
|---|---|---|
| FS | Start after the frame finishes | Days 21 to 24 |
| FS + 3 days lag | Start 3 working days after the frame finishes | Days 24 to 27 |
| FS with a 2 day lead (FS - 2) | Start 2 working days before the frame finishes | Days 19 to 22 |
| SS + 4 days lag | Start 4 working days after the frame starts | Days 15 to 18 |
| FF | Finish no earlier than the frame finishes | Days 17 to 20 |
| SF | Finish no earlier than the frame starts | Days 7 to 10 |
The same two tasks give finish dates eight working days apart only by changing the link type. The FS link is the one a reader assumes when nothing else is said, which is why a plan built mostly from FS links is the easiest to check.
What goes wrong in practice
- Leads used to squeeze a late plan: the successor starts before the work it depends on is done, and nobody can measure progress on the overlap.
- A lag standing in for work that has an owner, such as approvals or deliveries. Put that work in as a task, so it can be tracked and can slip visibly.
- Start to start links with nothing controlling the successor's finish, so the successor can run on past the end of the work that feeds it.
- Start to finish used where finish to start was meant. Real SF cases are rare, such as an old system kept running until the new one starts.
- Links to or from summary tasks, which hide which piece of work actually drives the date.
See this in your own file
Upload an .mpp, .xml or .xer file and see whether your links pass the DCMA limits: no leads, lags on at most 5% of links, at least 90% finish to start.
Check the links in your own scheduleLonger read: Dependency Types in Project Management: FS, SS, FF and SF
Questions
Which dependency type is the most common?
Finish to start. The DCMA 14-point assessment expects at least 90% of a schedule's links to be finish to start, because it is the plain reading of a dependency and the easiest to check against progress.
What is the difference between a lead and a lag?
A lag adds waiting time to a link, so the successor moves later. A lead is a negative lag, so the successor moves earlier and overlaps its predecessor. The DCMA assessment allows no leads at all.