Dependencies and Sequencing in Project Scheduling

Every project manager has encountered the challenge of building a schedule that reflects reality rather than wishful thinking. The difference between a schedule that teams can actually execute and one that collapses at first contact often comes down to how well you've modeled dependencies and sequenced activities. Understanding these relationships isn't just about drawing arrows between boxes on a Gantt chart—it's about capturing the true logic of how work must flow through your project.

For PMP candidates preparing under the July 2026 examination update, dependencies and sequencing remain foundational concepts tested across the Process domain (41% of exam weight). While PMBOK 8th Edition emphasizes principles over prescriptive processes, the mechanics of schedule development still demand precision. Whether you're working in a predictive, agile, or hybrid environment, you'll need to demonstrate mastery of dependency types, sequencing logic, and the relationship between schedule constraints and project outcomes.

Understanding the Four Types of Dependencies

Dependencies describe the logical relationships between project activities. The PMP exam tests your ability to identify which type applies in specific scenarios and how each affects your scheduling options.

Finish-to-Start (FS) represents the most common relationship: Activity B cannot start until Activity A finishes. In construction, you cannot begin framing walls (Activity B) until the foundation is poured and cured (Activity A). This dependency type accounts for approximately 90% of all schedule relationships in typical projects. When you encounter an exam question about "normal sequencing" or "typical workflow," assume FS unless the scenario explicitly indicates otherwise.

Start-to-Start (SS) means Activity B cannot start until Activity A starts, though they can run concurrently afterward. Consider software development where user acceptance testing (Activity B) can begin once developers start coding specific modules (Activity A)—you don't need to wait for all coding to finish. This relationship often includes a lag, such as "Testing can start 5 days after coding begins." On the exam, watch for scenarios describing parallel work streams with staggered starts.

Finish-to-Finish (FF) requires Activity B to finish no earlier than Activity A finishes. Quality documentation (Activity B) must be completed by the time testing (Activity A) concludes—both need to wrap up together, though documentation might have started earlier. FF dependencies appear less frequently than FS or SS relationships but become important when coordinating deliverables that must be completed simultaneously. A practical example: final client training materials must be complete when the training program ends, not necessarily when it begins.

Start-to-Finish (SF) is the rarest dependency type, where Activity B cannot finish until Activity A starts. This counterintuitive relationship appears in just-in-time scenarios—for instance, maintaining an old system (Activity B) cannot stop until the replacement system (Activity A) goes live. On the PMP exam, SF dependencies rarely appear, but when they do, the question typically involves transition scenarios or system cutover situations.

Practice identifying these relationships in context rather than memorizing definitions. When working through questions at pmp-guide.com, pay attention to the specific wording describing how activities relate to each other. The exam writers deliberately use realistic project scenarios rather than abstract definitions.

Sequencing Methods and Network Diagrams

Sequencing transforms your activity list into a logical model showing how work flows through the project. The primary tool for visualizing this logic is the precedence diagramming method (PDM), which uses boxes (nodes) to represent activities and arrows to show dependencies.

In PDM, each activity appears as a node containing key information: activity identifier, duration estimate, and sometimes early/late start and finish dates. The arrows between nodes represent logical relationships, not durations—a common misconception that trips up exam candidates. A long arrow and a short arrow both simply indicate "these activities are related"; arrow length has no scheduling meaning in PDM.

The network diagram reveals your project's critical path—the longest sequence of dependent activities from project start to finish. Any delay to a critical path activity delays the entire project, making these activities your highest scheduling priority. Non-critical activities have float (also called slack), representing how much they can slip without affecting the project end date. Understanding float calculation remains essential for the PMP exam because it determines where you have scheduling flexibility versus where delays cascade immediately.

Consider a software deployment project with parallel tracks: one for development, one for infrastructure preparation. If development takes 45 days and infrastructure takes 30 days, development represents the critical path. Infrastructure activities have 15 days of total float—they could slip by up to 15 days without delaying project completion. However, if infrastructure slips by 20 days, it becomes the new critical path, extending the project by 5 days beyond the original schedule.

Lags and leads modify dependency relationships to reflect real-world constraints. A lag inserts waiting time between activities, such as requiring concrete to cure for 3 days before proceeding to the next construction phase. Leads allow acceleration by starting a successor activity before its predecessor completes, though leads should be used sparingly as they increase risk. A 2-day lead on an FS relationship essentially converts it to an SS relationship with a lag of (predecessor duration - 2 days).

When building network diagrams, avoid these common mistakes: creating activities with no predecessors (excep