Predecessors can be added to any task either inline or in the full task edit screen. Below shows the predecessor tab on the task full edit screen. PI does not recommend setting predecessor relationships on Summary tasks based on the PMBOK methodology.
This window is for defining a relationship between the new task that is being defined, called the successor, and another task, called its predecessor. You can use it to establish that this task should begin only after a predecessor task has been completed, that this new task should begin only after the predecessor task has begun, or another relationship type specification. This form can also be used to add predecessors from other projects if the Cross Project Dependencies have been set.
Task offers a menu of existing tasks that can be chosen to begin establishing the relationship with the task being created.
Lead/Lag indicates the amount of lead time or lag time that should be allowed in between the selected task and the task being defined.
Days and hh:mm indicates the amount of Lead or Lag time to apply. Enter the number of days and/or hours and minutes of Lead or Lag time. Leave the field set to 0 days if no Lead or Lag time is desired, such as when the task being defined should begin immediately upon completion of the predecessor task. As with duration settings for the task, the use of whole day values is recommended, avoiding any hours and minutes duration calculations.
Type is for selecting the type of relationship that should be created. Choices include:
- Finish-to-Start: Specifies that the successor task is not to be started until the predecessor task (or Summary Task) has been completed.
- Start-to-Finish: Requires that the successor task not be completed until the predecessor task has begun.
- Start-to-Start: Means that the successor task should not be begun until the predecessor task has begun.
- Finish-to-Finish: Indicates that the successor task not be finished until the predecessor task has been finished.
Example 1:
If you were to create a Summary Task called Budget Approval, then create a successor task called Prepare Samples, you could specify that Prepare Samples have a Finish-to-Start relationship with Budget Approval, which would appear on the Gantt chart as it does below.
This shows graphically that Prepare Samples can't begin until Budget Approval has been completed.
Example 2:
Using the Budget Approval predecessor task and Prepare Samples successor task from Example 1, you could specify that Prepare Samples have a Start-to-Finish relationship with Budget Approval. The Gantt chart would show this relationship graphically as it does in the window below.
See Adding Predecessors in the Task Entry section for more usage detail on the predecessor selection interface.
Comments
6 comments
Hi Alex,
Are these options applicable to Start/End (Schedule) Date or Actual Start/End date?
Predecessors will change the start/end date scheduled, but not the actual dates. The actual dates are changed based on other settings to compare the schedule versus the actual. For example, the actual can be set to change based on the date a resource updates that they started and the date they update that they completed it.
Thank you Wes.
Wes, one more question.
What if we have the following option enable "Automatically Calculate Task Schedule Based on Actual Start and End Dates“
User updates the task's actual start date ahead of planned start date. Since we the option above enabled, it will update the planned start date as well, and assuming the task has lag option Finish-to-Start and its predecessor is not yet 100% completed. What will happen?
Hello Junpei,
Once the resource marks the predecessor task complete, the successor task's start date will adjust due to your "Automatically Calculate Task Schedule Based on Actual Start and End Date" settings.
This setting can delay your project plan if a task's actual end date is later than the schedule OR accelerate your project plan if a task's end date is earlier than expected.
This feature is very powerful, but it also adjusts your schedule automatically, so you have to keep a close eye on resource's updating their tasks correctly.
Thank you Margaret.
Please sign in to leave a comment.