Skip to content
PMPCAPM

Finish-to-Finish (FF) Dependency

A Finish-to-Finish (FF) dependency is a logical relationship in which a successor activity cannot finish until a predecessor activity has finished.

Share:

Know it well enough for the exam? Questions on Finish-to-Finish (FF) Dependency are scenario-based, not definitional.

Practice it free

Explanation

Finish-to-Finish dependencies link the completion of two activities together. The successor activity can start independently, but it cannot be marked as complete until the predecessor has also been completed. This is useful when two parallel activities must end at roughly the same time or when the completion of one activity depends on data or deliverables from the completion of another.

For example, writing a document (predecessor) and editing that document (successor) might have an FF relationship. Editing cannot finish until writing finishes because the editors need the final written content before they can complete their review. The editing may have started earlier, but its completion depends on the writing being done.

FF dependencies are often paired with SS dependencies to create a fully constrained pair of parallel activities. Together, SS and FF relationships ensure that two activities start in a controlled sequence and also finish in a controlled sequence. Lags can be applied to FF relationships to introduce a delay between the finish of the predecessor and the allowed finish of the successor.

Key Points

  • •Successor cannot finish until predecessor finishes
  • •Activities can run in parallel but must finish in sequence
  • •Often paired with SS dependencies for fully constrained parallel work
  • •Lags can offset the finish times between activities

Exam Tip

FF does not mean both activities finish at the same time. It means the successor is not allowed to finish until after the predecessor finishes.

Frequently Asked Questions

Related Topics

High-yield topics our learners drill most before exam day.

Resource Leveling

Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.

Critical Path Method (CPM)

The Critical Path Method (CPM) is a schedule network analysis technique that calculates early and late start and finish dates for every activity to find the longest path through the project, the minimum project duration, and the float on every other path.

Resource Smoothing

Resource smoothing is a resource optimization technique that adjusts activities within their available float so that resource requirements do not exceed predefined limits, without changing the project end date.

Burndown Chart

A burndown chart plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.

Burn-Up Chart

A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.

Deliverables

A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.

Power Interest Grid (Power/Influence Grid)

The power interest grid is a 2x2 stakeholder mapping tool that plots each stakeholder by power (ability to affect the project) and interest (concern about its outcome) to decide how to engage them: manage closely, keep satisfied, keep informed, or monitor.

Weighted Shortest Job First (WSJF)

Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.

Risk Register

The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.

Part of

Schedule Management

Study full domain →

Practice Finish-to-Finish (FF) Dependency

Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.