Contents of the Dependency Details Dialog Box

Use these fields to view WBS element details and to add, update, or remove dependencies between predecessors and successors. You can also add lag and lead time to dependencies if needed.

Contents

Field Description
Plan Structure Branch This field displays the selected work breakdown structure (WBS) element along with the path making up this branch of the plan WBS. Click the link to display a snapshot of the project's details.
Description This field displays a description of the selected WBS element.
Plan Start/Plan End These fields display the plan start and end dates for the selected WBS element.
Duration This field displays the span of time between the start and end dates, expressed in working days.
Notes Use this text entry field to view or record any plan-related notes or details for the selected WBS element.

Dependencies Grid

While building your project schedule, you can set up relationships between the WBS elements. These relationships are also known as dependencies. You can structure dependencies logically so that certain levels rely on the start or completion of other levels before they can be started or completed. Establishing schedule dependencies makes it possible to keep close track of your project's critical path and overall schedule, identify potential schedule risks, and streamline the update process when the schedule changes.

For more information about how dependencies work across different WBS levels, types of dependency relationships, and how lead/lag and float time impact dependency relationships, see Working with Schedule Dependencies.

When you create a dependency, you must consider the plan's WBS structure and the type of relationship that you want to create between levels, including which is the predecessor and which is the successor. In the most common dependency relationship, the predecessor must finish before the successor can start. This is called a Finish-to-Start relationship and is described in the Relationship section below.

You can create more than one unique relationship between the same two levels in a plan, as long as each relationship has the same direction. However, if you try to create a new dependency in which a relationship level would have a dependency on itself, this causes a circular dependency, which is not allowed. If this happens, the predecessor or successor text for all rows impacted by the circular dependency turns red and the Circular Dependency Not Allowed dialog box opens so you can review a list of the relationships that caused the problem. For more details, see Circular Dependency Not Allowed Dialog Box.

Field Description
Predecessor The first item that you select in each relationship is considered the predecessor. This item leads the relationship. The earliest possible start or end dates for the current WBS element are determined by the dates of its predecessor along with the type of relationship and lag or lead days selected. To add a predecessor, click +Add Predecessor and select a level that the current WBS element will depend on.

Only the allowed levels are available for selection. You cannot create relationships with parent and child levels since they already have an inherent relationship. For more information, see HOw Dependencies Work Across Different Levels.

Successor The second level that you select in the relationship is considered the successor. This item is impacted by the predecessor. To add a successor, click +Add Successor and select a level that will depend on the current WBS element.
Relationship To specify the dependency between the predecessor and the successor, select a relationship type:
  • Finish-to-Start: The predecessor must finish before the successor can start. This is the most common relationship used when planning projects.
  • Start-to-Start: The predecessor must start before the successor can start.
  • Finish-to-Finish: The predecessor must finish before the successor can finish.
  • Start-to-Finish: The predecessor must start before the successor can finish.

When you create the dependencies, an arrow displays on the Gantt chart, linking each predecessor to the successor.

Lag (+) or Lead (-)

Use lag or lead time to specify a delay (lag) or an overlap (lead) between elements in a given relationship. Be aware that adding lag time can extend the plan dates.

Specify the lag or lead time for the level in working days. Click the up or down arrow to change values or enter the number of days of lag (positive number) or lead (negative number). The maximum allowed value is 4000. Decimal places are not allowed.

  • Lag: Indicates a delay between the predecessor and successor relationship, in working days.

    For example, if the Relationship is Finish-to-Start, you can specify a lag time of five days so that the successor does not start until five days after the predecessor is finished.

  • Lead: Indicates an overlap in the predecessor and successor relationship, in working days.

    For example, if the Relationship is Finish-to-Start, you can specify a lag time of five days so that the successor can start five days before the predecessor task is finished.

Apply Click this option to save your entries.