Activity Dependencies

AI Summary

An AI-generated summary of this video lecture.

This lecture introduces the four standard activity dependency types used in project scheduling: Finish-to-Start (FS), Start-to-Start (SS), Finish-to-Finish (FF), and Start-to-Finish (SF). The instructor presents each dependency with a rule statement, a concrete example, and hand-drawn annotations on the slide. FS is introduced first using a construction sequence (Foundation → Framing → Roofing) and the rule that Activity B starts after Activity A finishes, with a coding/testing example. SS is then defined as both activities starting together, illustrated by UI Design and Database Design beginning simultaneously; the instructor circles the SS symbol and highlights the start-to-start image. FF is defined as both activities finishing together, illustrated by Documentation being completed when Testing is completed, with a checkmark placed beside the FF heading. Finally, SF is presented as the rare case where Activity B finishes only after Activity A starts, illustrated by an old server remaining active until a new server starts; the instructor adds a checkmark beside SF and draws A/B arrows near the top of the slide. The progression moves from the most common dependency (FS) through the parallel dependencies (SS, FF) to the rare reverse dependency (SF), consistently pairing each rule with a real-world example.

Chapters

1. 0:00 – 2:00 00:00-02:00

   The instructor introduces Activity Dependencies, beginning with Finish-to-Start (FS), shown on-screen as 'Rule: Activity B starts after Activity A finishes' with the example 'Coding must finish before Testing begins.' A construction diagram labels FOUNDATION, FRAMING, and ROOFING under 'TASK DEPENDENCE,' and handwritten annotations mark 'A End' and 'B Start.' The lesson then moves to Start-to-Start (SS), displayed as 'Rule: Both activities start together' with the example that UI Design and Database Design start simultaneously; the instructor draws a red circle around the SS symbol and highlights the START TO START image. Next, Finish-to-Finish (FF) appears as 'Rule: Both activities finish together,' with the example that Documentation is completed when Testing is completed, and a checkmark is placed beside the FF heading.

2. 2:00 – 2:29 02:00-02:29

   The final dependency, Start-to-Finish (SF), is presented under the heading '4. Start to Finish (SF)' with the on-screen rule 'Activity B finishes only after Activity A starts (rare).' The example describes an old server remaining active until the new server starts. In later frames, red handwritten marks appear: a checkmark beside 'Start to Finish (SF)' and the letters A and B with arrows drawn near the top of the slide, visually linking the start of one activity to the finish of another.

The core teaching point is that project activities are linked by four dependency types, each defined by which event (start or finish) of Activity A controls the corresponding event of Activity B. FS is the default, sequential relationship (A finishes before B starts), illustrated by construction phases and coding/testing. SS allows parallel work to begin together (UI Design with Database Design). FF requires parallel work to end together (Documentation with Testing). SF is the rare reverse case where B finishes only after A starts, illustrated by an old server staying active until a new one starts. The instructor reinforces each type with a rule line, an example line, and hand-drawn symbols (circles, checkmarks, A/B arrows), helping students distinguish the four relationships for scheduling and exam recall.