Activity Sequencing and Dependencies

Activity Sequencing and Dependencies involves identifying the logical relationships between project activities to determine the order in which they must be performed. This process is fundamental in software project scheduling, enabling the creation of a realistic and efficient timeline by establishing how activities depend on one another, thereby influencing start and finish times.

Definition and Purpose

Activity sequencing is the process of arranging project activities in the most logical order based on their dependencies. Dependencies indicate the constraints that govern whether an activity can start or finish relative to other activities. Understanding these relationships ensures that activities are scheduled realistically, avoiding conflicts and optimizing resource usage. It supports critical path analysis, risk management, and overall schedule accuracy.

Types of Schedule Dependencies

Schedule dependencies specify the nature of the relationship between two activities. They can be classified as follows:

Mandatory Dependencies

Also known as hard logic, mandatory dependencies are inherent in the nature of the work or required by contract, law, or physical constraints. These cannot be changed without altering the project scope or product. For example, construction of a foundation must be completed before erecting walls.

Discretionary Dependencies

Also referred to as soft logic or preferential logic, discretionary dependencies are based on best practices, organizational preferences, or sequencing chosen by the project team. They can be modified if necessary. For example, choosing to perform software module testing after code review is a discretionary dependency.

Internal Dependencies

These occur between activities within the project that are under the control of the project team. They often involve technical or procedural constraints internal to the project.

External Dependencies

External dependencies involve relationships between project activities and external factors outside the project's control, such as delivery of equipment by a supplier or government approvals.

Types of Activity Dependency Relationships

Dependencies are often expressed using four primary logical relationships that define how activities relate in terms of start and finish times:

Finish-to-Start (FS)

This is the most common dependency, representing a sequential relationship where one activity must be completed before the next begins.

Start-to-Start (SS)

Activities can start simultaneously or overlapping, but the successor cannot start before the predecessor starts.

Finish-to-Finish (FF)

The successor activity's completion depends on the predecessor finishing, allowing overlapping execution.

Start-to-Finish (SF)

Rarely used, where the successor cannot finish before the predecessor starts, typically in just-in-time or handover scenarios.

Schedule Leads and Lags

Leads and lags modify the basic dependencies by adding time offsets:

• Lead allows an acceleration of the successor activity’s start or finish, effectively overlapping activities. For example, starting testing two days before coding finishes.
• Lag introduces a delay between activities, representing waiting or buffer time. For example, waiting 3 days after pouring concrete before starting framing.

Leads are represented as negative lag values in scheduling tools.

Schedule Dependency Validation

Validating activity dependencies ensures logical consistency and feasibility of the project schedule. It involves:

• Checking for circular dependencies that create impossible loops.
• Verifying that mandatory dependencies are correctly applied.
• Confirming that external dependencies are accounted for with proper contingencies.
• Ensuring that leads and lags reflect realistic overlaps or delays.
• Maintaining alignment with project goals and constraints.

Dependency validation minimizes risks of schedule conflicts, resource bottlenecks, and missed deadlines.

Visual Representation of Activity Dependencies

Activity sequencing is often visualized using network diagrams, showing activities as nodes and dependencies as connecting arrows labeled with dependency types and lead/lag times.

This diagram illustrates the four main dependency types connecting activities, with solid lines for common dependencies and dashed lines for less common ones.

Summary

Activity sequencing and dependencies form the backbone of effective software project scheduling by defining how tasks relate and constrain each other. Proper identification and management of dependencies—including mandatory, discretionary, internal, and external—combined with accurate use of dependency relationships and lead/lag adjustments, enable realistic and manageable schedules. Validating dependencies ensures project feasibility and helps avoid delays, resource conflicts, and rework, ultimately contributing to project success.