Understanding Project and Task Dependencies

project manager analyzing project tasks written on sticky notes
GettyImages/Bernd Opitz

Project Managers reference project dependencies as the relationships between individual tasks in a project. diagram. Preceding tasks must be completed before moving on to the next or succeeding tasks. All of the tasks required to achieve the project's scope are sequenced according to their dependencies for each other, and then resources are linked to the tasks and a project schedule constructed. 

The project or task dependencies are critical for:

  • Sequencing the work packages (tasks) in a project plan.
  • Calculating the critical path (longest path/duration) of tasks in a project plan. 
  • Identifying resource and scheduling issues and making supporting decisions. 
  • Monitoring and managing as part of the overall project plan. 
  • Identifying opportunities to accelerate the schedule via fast-tracking or crashing. 

Examples of Project Task Dependencies:

While the analysis of task dependencies for a large project is a complex task often requiring computer software, consider a few simple examples to illustrate the concept. 

Example 1: Making coffee. Imagine getting out of bed in the morning, yawning and making your way to the kitchen to discover that you forgot to preset your coffeemaker to brew automatically. It is now up to you to shake off the sleep and start the coffee brewing. You know that you need to complete the following tasks:

  • Add water
  • Grind the coffee beans
  • Measure the coffee into the filter
  • Add a coffee filter
  • Place the carafe on the heating tray
  • Press brew

Of course, there is a proper order to this process. You would not press brew before completing all of the other steps. A proper sequence of events taking into account dependencies might be as follows:

  1. Grind the coffee beans
  1. Add a coffee filter 
  2. Measure the coffee into the filter
  3. Add water
  4. Place the carafe on the heating tray
  5. Press brew.

In this sequence of tasks, you could not measure the coffee into the filter before you ground the beans. Grinding the coffee beans is a predecessor activity for measuring the coffee into the filter. The measuring step is a succeeding activity. All of the tasks are predecessor activities to the step: Press Brew. 

Example 2: Installing a lawn and lawn sprinkling system in a brand new house. Important tasks include:

  • Install the sod (lawn)
  • Dig the trenches for and install the sprinkling system hoses
  • Locate the sprinkler heads
  • Grade the lot
  • Fill the trenches

The proper sequence of events taking into account task dependencies is:

  1. Grade the lot.
  2. Locate the sprinkler heads.
  3. Dig the trenches for and install the sprinkling system hoses. 
  4. Fill the trenches
  5. Install the lawn. 

Understanding the dependencies in this example allows the landscaper to plan for grading and digging equipment, ensuring the availability of supplies and scheduling the proper resource for each step. 

Types of Project Planning Dependencies:

There are four types of project planning dependencies. They establish the relationships among the tasks.

They are listed in the order most often used.

  1. Finish To Start (FS). The first task must complete before the second task can start. For example, the task "Write code module 1" must finish before the task "test code module 1" can begin.
  2. Finish To Finish (FF). The second task cannot finish before the first task finished. The task "all code tested" cannot finish before the task "test code module x" finishes.
  3. Start To Start (SS). The second task doesn't start until the first task starts. The task "write training manual" must start before the task "write chapter 1 of training manual" can start.
  4. Start To Finish (SF). The first task must start before the second task can finish. The task "assign coder for module 3" must start before the task "all work assigned" can finish.

    Categories of Project Planning Dependencies

    There are also dependencies with other projects. Planning dependencies fall into three categories: logical, resource-based, or preference. There are four types of project planning dependencies.

    • Logical Planning Dependencies: These are dependencies that are logic driven. You can't paint a wall before it's built. You can't test a code module until after it's written.
    • Resource-based Planning Dependencies: These are dependencies where the task could be accomplished faster or sooner if you had more resources. The manual could be written faster if you had more than one writer. You could write more code except all the other developers are committed to other projects.
    • Preference Planning Dependencies: These are tasks that could be scheduled differently, but the Project Manager chooses to schedule this particular order.

    The Bottom Line: 

    Project Managers must be able to plan for and manage the dependencies among tasks in their projects. Dependencies impact scheduling and resource activities and it is critical to understand these relationships when looking for opportunities to improve the project schedule. 

    --

    Updated by Art Petty