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:

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 in which adjustments are made to the project schedule to keep resource usage at or below a defined limit, often resulting in a longer project duration.

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 is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.

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.

Stakeholder Mapping

Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.

Relative Estimation

Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.

Cost Performance Index (CPI)

Cost Performance Index (CPI) is an EVM efficiency metric that measures cost performance as the ratio of earned value to actual cost: CPI = EV / AC.

Schedule Performance Index (SPI)

Schedule Performance Index (SPI) is an EVM efficiency metric that measures schedule performance as the ratio of earned value to planned value: SPI = EV / PV.

Earned Value Management (EVM)

Earned Value Management (EVM) is a methodology that integrates scope, schedule, and cost data to assess project performance and progress objectively.

Part of

Schedule Management

Study full domain →

Test your knowledge

Practice scenario-based questions on this topic with detailed explanations.