Finish-to-FinishWith a finish-to-finish (FF) and zero lag, the successor activitycan finish at the same time or later than the predecessor activityfinishes, so that the earliest possible finish time of the successor isthe same day of the predecessor’s EFT. For example, as shown inFig. 11, Activity A finishes at the end of Day 5, thus its successorswith FF:0 can finish at the same time or later. Since Activity Bbelongs to Calendar 2, it cannot finish on Day 5. Activity B can finish at the end of Day 8, which is the next available workingday on Calendar 2.With a FF and positive lag, the successor can finish at the lagtime after or later than the predecessor finishes, so that the earliestpossible finish time of the successor is the day of the predecessor’sEFT plus the amount of the lag time counted by workingdays on the predecessor’s calendar. For example, as shown in Fig.12, Activity A finishes at the end of Day 5, thus its successorswith FF:1 can finish at the end of Day 8 or later. Since Day 8 is aworking day in Calendar 2, Activity B can finish at the end ofDay 8.With a FF and negative lag, the successor can finish at the lagtime before or later than the predecessor finishes, so that the earliestpossible finish time of the successor is the day of the predecessor’sEFT less the amount of the lag time counted by workingdays on the predecessor’s calendar. For example, as shown in Fig.13, Activity A finishes at the end of Day 5, thus its successorswith FF:−1 can finish at the end of Day 4 or later. Since ActivityB belongs to Calendar 2, it cannot finish on Day 4. Activity B canfinish at the end of Day 8, which is the next available workingday on Calendar 2.