Types of Dependencies: FS, SS, FF, SF
You'll learn the four fundamental dependency relationship types that govern task ordering in project schedules.
The Core Idea
When mapping project dependencies, not every task follows a simple "finish one, start the next" pattern. There are actually four types of dependency relationships that describe how the start or finish of one task relates to the start or finish of another:
Finish-to-Start (FS) — The Default
Task B cannot start until Task A finishes. This is the most common dependency: you finish writing code, then you start code review.
Analogy: You must finish baking a cake before you can start frosting it.
Start-to-Start (SS)
Task B cannot start until Task A starts. Both tasks run in parallel, but B depends on A beginning first.
Analogy: A backend developer starts building an API, and the frontend developer can start building UI components once the API design begins (not waiting for completion).
Finish-to-Finish (FF)
Task B cannot finish until Task A finishes. B might start earlier, but its completion is tied to A's completion.
Analogy: Integration testing can't finish until the final feature implementation finishes, even though testing started earlier.
Start-to-Finish (SF) — The Rare One
Task B cannot finish until Task A starts. This is uncommon but appears in handoff scenarios.
Analogy: An on-call engineer can't finish their shift until their replacement starts theirs.
Why This Matters
Understanding these relationships lets you model realistic project schedules. Not everything is sequential (FS). Recognizing SS and FF dependencies helps you identify parallel work opportunities, reducing project duration while respecting true constraints.
Key Takeaway: The four dependency types (FS, SS, FF, SF) define precise relationships between task starts and finishes, enabling accurate scheduling and identification of parallelization opportunities.