According to the provided reference, an FF relationship (Finish to Finish) is a type of logical relationship between two activities in project management. It indicates that the completion of the predecessor activity is necessary for the successor activity to begin. This type of dependency is also known as “end-to-end” or “finish-to-finish” in this context.
Understanding Task Dependencies
In project management, tasks rarely exist in isolation. They often depend on the completion or start of other tasks. These links are called dependencies or logical relationships. Identifying and managing dependencies is crucial for creating an accurate project schedule.
The provided reference describes the FF relationship as:
- Type: Logical relationship between two activities.
- Condition: Completion of the predecessor activity is required.
- Outcome: The successor activity can then begin.
This description aligns with what is commonly known as a Finish-to-Start (FS) dependency in standard project management practices, where Activity A must finish before Activity B can start. While the reference uses the term "Finish to Finish (FF)" and lists "end-to-end" or "finish-to-finish" as aliases, the definition provided within the reference specifically describes the predecessor's finish enabling the successor's start.
Why Use This Type of Dependency (as defined in the reference)?
Dependencies where one task must finish before another can start (the definition given for FF in the reference) are the most common type in project scheduling. They represent a natural progression of work.
Key practical insights for using this dependency type include:
- Sequential Work: Many tasks must happen in a specific order (e.g., design must finish before construction starts).
- Resource Constraints: Often, the same resources are needed for subsequent tasks, requiring the first task to be completed to free up resources.
- Information Flow: The output of one task (the predecessor) is the input for the next task (the successor).
Examples Based on the Reference's Definition
Based on the definition provided (predecessor finishes -> successor starts), here are some examples:
- Example 1:
- Predecessor: Pour the concrete foundation.
- Successor: Begin framing the walls.
- Relationship: The foundation must be completely poured and set before wall framing can start.
- Example 2:
- Predecessor: Write the project report draft.
- Successor: Submit the report for review.
- Relationship: You must finish writing the draft before you can start the process of submitting it.
- Example 3:
- Predecessor: Conduct the final quality inspection.
- Successor: Package the product for shipping.
- Relationship: The inspection must be finished to ensure the product meets standards before packaging can begin.
How Dependencies Link Tasks
Dependencies are visualized in project schedules using arrows linking activities. The type of arrow or notation indicates the specific relationship. For the relationship type described in the reference (predecessor finishes enabling successor start), a link would typically go from the end point of the predecessor task bar to the start point of the successor task bar in a Gantt chart.
Here's a simple illustration using the reference's definition:
| Task (Activity) | Dependency Type (as per reference) | Dependent Task (Activity) | Rule (as per reference) |
|---|---|---|---|
| Task A (Predecessor) | FF | Task B (Successor) | Task A must finish before Task B can begin. |
| Write Code (Predecessor) | FF | Test Code (Successor) | Writing the code must finish before testing the code can begin. |
Understanding these relationships is vital for building a realistic project timeline, identifying the critical path, and managing project risks effectively.
