Task Dependencies in Microsoft Project 2010

And once again, I would be willing to bet money that many of the users of Microsoft Project never change the default task dependency types within their project schedules.

image

The 4 types of Task Dependencies in Project 2010 are:

  1. Finish-To-Start (FS) – the initiation of the successor task depends on the completion of its predecessor
  2. Finish-To-Finish (FF) – the completion of the successor task depends on the completion of its predecessor
  3. Start-To-Start (SS) – the initiation of the successor task depends on the initiation of its predecessor
  4. Start-To-Finish (SF) – the completion of the successor task depends on the initiation of its predecessor

The most common and default type of task dependency found in project schedules are the Finish-To-Start (FS) dependencies.

Leads and Lags:

In addition to selecting a type of dependencies between tasks, you also have the option of assigning leads and lags on the relationship.

  • Lead – a lead allows for the acceleration of the successor task. For example, the landscaping can be scheduled to start three weeks prior to the completion of the construction of the house. This would be a Finish-To-Start task dependency with a three week lead.
  • Lag – a lag is a delay in the successor activity. For example, the editing of an instruction manual could begin one week after the technical writers have begun. This would be a Start-To-Start task dependency with a one week lag.

3 thoughts on “Task Dependencies in Microsoft Project 2010

  1. You will make it seem so easy along with your demonstration however I obtain this matter to generally be really the one thing that I believe that I would never have an understanding of. It seems like very challenging as well as huge for me. I’m just writing about in advance in the subsequent distribute, I will seek to have the dangle than me!

  2. Hi Matthew

    I try to get he most out of MS Project but i believe i can’t really use the basic task dependencies.

    I have a project which includes site deployments in the telco industry. A site build has many different stages which are actually sub projects in the actual project.

    Here is the problem.
    A certain milestone is the trigger so that installs and logistic activities can be planed, which is called transmission (TX).

    I receive the forecast dates for the TX availability which is the trigger for me to plan the call off of the hardware and resources to do the install on the day of TX availability minus i.e 9 days for shipping lead time.

    The above activities have to happen prior the TX forecast to ensure that material etc. is available once the transmission has been actualized.

    which task dependency would make sense a finish to start between logistics call off or shipping and the TX forecast minus the lead time how long it takes to ship the hardware to site or a start to start dependency between logistics call off and TX availability minus the lead time of how long it takes to ship the material.

    Cheers
    Chris

Comments are closed.