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 questions). 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 (except the project start), creating activities with no successors (except the project end), or allowing loops that create circular logic. Each of these represents a logical flaw that makes your schedule unworkable. The PMP exam often includes questions asking you to identify which network diagram correctly represents a described scenario.

Mandatory, Discretionary, External, and Internal Dependencies

Beyond the FS/SS/FF/SF classification, dependencies also categorize by their source and whether they're truly required. This classification helps project managers understand where they have flexibility versus where they're locked into specific sequences.

Mandatory dependencies (hard logic) derive from the inherent nature of the work or from contractual/legal requirements. You must install electrical wiring before installing drywall in construction projects—the work itself dictates this sequence. Similarly, regulatory approval must occur before product launch in pharmaceutical projects. On the exam, mandatory dependencies cannot be modified or removed regardless of time pressure. Questions testing this concept often present scenarios where the sponsor wants to accelerate the schedule and asks which dependencies you can eliminate—mandatory ones remain fixed.

Discretionary dependencies (preferred logic or soft logic) reflect best practices or organizational preferences but could theoretically be rearranged. Your company might prefer to complete requirements documentation before beginning design work, but these phases could overlap if schedule pressure demands it. Discretionary dependencies offer opportunities for fast-tracking—performing sequential activities in parallel to compress the schedule. However, fast-tracking increases risk because you're proceeding with incomplete information from predecessor activities.

External dependencies involve relationships with parties outside the project team. Waiting for a vendor to deliver equipment, receiving regulatory approval, or depending on another project team to complete their deliverable all represent external dependencies. These warrant special attention because they're outside your direct control. The project manager's options with external dependencies focus on influence and contingency planning rather than direct management. Contract terms, service level agreements, and escalation procedures become your primary risk mitigation tools.

Internal dependencies exist within the project team's control. Assigning a senior developer to review code before it moves to testing represents an internal dependency that the project manager can directly manage through resource allocation, priority setting, and work assignment decisions.

Practical application requires distinguishing these categories correctly. During schedule compression, you can modify discretionary dependencies but not mandatory ones. When identifying risks, external dependencies typically warrant more contingency buffer than internal ones because you have less control. A realistic project schedule might show an external dependency (vendor delivery) with three weeks of buffer built in, while an internal dependency (internal review) might need only three days.

The 2026 PMP exam increasingly emphasizes adaptive approaches where dependency management becomes more dynamic. In agile or hybrid projects, you still need to understand these relationships, but you manage them through iteration planning and dependency boards rather than detailed network diagrams created months in advance. A user story might be blocked by an external dependency (API access from a third party), requiring the team to resequence their sprint backlog.

Practical Scheduling Techniques and Common Pitfalls

Theory becomes valuable only when applied correctly. Several practical techniques and awareness of common mistakes separate effective schedulers from those whose timelines consistently prove unrealistic.

Resource leveling adjusts activity start dates based on resource constraints. Your network diagram might show two activities can start simultaneously, but if both require your only specialized tester, you must sequence them. Resource leveling often extends the schedule because it serializes work that was logically parallel. This frequently appears on PMP exam questions asking "What happens to the project duration when resource leveling is applied to a resource-constrained schedule?" The answer: duration increases or stays the same, never decreases.

Resource smoothing adjusts activities within their available float to reduce period-by-period variations in resource demand, but without extending the schedule beyond the original critical path. Unlike leveling, smoothing maintains the project end date as fixed, making it useful when you have a hard deadline that cannot move. The exam may present scenarios where you need to choose between these techniques based on whether the deadline or resource utilization takes priority.

Critical chain method recognizes that resource dependencies matter as much as logical dependencies. Traditional critical path analysis assumes unlimited resources, but critical chain creates a more realistic schedule by accounting for resource constraints from the start. It also addresses human behavior by removing safety buffers from individual activities and aggregating them as project buffers, preventing Parkinson's Law (work expands to fill available time) from consuming all your contingency.

Common scheduling pitfalls include failing to update dependencies as the project evolves, assuming all FS relationships when other types better reflect reality, and overlooking resource constraints when building the initial network diagram. Another frequent error involves confusing constraints with dependencies. A constraint fixes a date ("Marketing launch must occur on November 1st"), while a dependency establishes a relationship between activities. The exam tests whether you recognize that constraints reduce scheduling flexibility while dependencies simply establish logical sequencing.

When working in agile environments, dependencies don't disappear—they simply manifest differently. Teams track dependencies on Kanban boards using blocked/blocking indicators, discuss them in daily stand-ups, and manage them through dependency walls or obeya rooms in scaled agile frameworks. A product owner must still understand that certain features depend on architectural decisions or infrastructure components before they can be developed. The sequencing principle remains constant even as the tools and cadences change.

Key Takeaways

Dependencies and sequencing form the logical foundation of every project schedule, regardless of approach. Master the four dependency types (Finish-to-Start, Start-to-Start, Finish-to-Finish, Start-to-Finish) and recognize that FS relationships dominate real-world projects while SF relationships rarely appear outside specific transition scenarios.

Understand that dependencies categorize both by their logical relationship (FS/SS/FF/SF) and by their source and flexibility (mandatory, discretionary, external, internal). This dual classification determines where you have scheduling options versus where you're locked into specific sequences.

The critical path represents your project's longest dependent sequence and therefore its minimum possible duration. Activities on the critical path have zero float—any delay cascades directly to the project end date. Non-critical activities have float, giving you flexibility in when to schedule them within their early and late date windows.

Network diagrams using precedence diagramming method (PDM) provide the visualization framework for dependency logic. These diagrams reveal the critical path, calculate float, and help you identify opportunities for schedule compression through fast-tracking (parallelizing sequential activities) or crashing (adding resources to critical path activities).

Resource constraints often override logical dependencies. Resource leveling extends duration to resolve resource conflicts, while resource smoothing adjusts activities within available float to balance resource demand without changing the project end date.

In adaptive environments, dependency management becomes more dynamic but no less important. Teams track dependencies through different mechanisms (dependency boards, daily stand-ups, sprint planning) but still must sequence work logically and manage external dependencies that could block progress.

As you prepare for the Process domain questions on the PMP exam, practice applying these concepts to realistic scenarios rather than memorizing definitions. The exam presents situations where you must identify the correct dependency type, determine scheduling implications, or recommend appropriate actions when dependencies change. Working through practice questions at pmp-guide.com helps develop the pattern recognition needed to answer these questions confidently under time pressure during your 240-minute exam session.