Create program dependencies

Program dependencies are used to create dependencies between two programs on an epic or a capability as well as to create dependencies between program teams.

Create program dependencies on the dependencies page:

1. Select a portfolio, program, or team from the Teams dropdown in the top navigation bar.
2. On the sidebar, select More items in the list of options.
3. Select Dependencies; the dependencies page displays.

To create a program dependency between programs:

1. On the dependencies page, select the Add Dependency button on the toolbar (top-right of the page). The New Dependency slide-out panel displays.
2. Select the PI from the Program Increment dropdown menu, select Epic or Capability as a work item type for this dependency, and then select the epic or capability itself.
3. From the corresponding dropdown menus, select the Requesting program and the Depends On program.
4. In the Needed By box, use the calendar to select the date this dependency needs to be resolved by.
5. Click Save. The dependency is saved and additional fields display.

To create a program dependency between program teams:

1. On the dependencies page, select the Add Dependency button on the toolbar (top-right of the page). The New Dependency slide-out panel displays.
2. From the Program Increment dropdown menu, select the PI in which the dependency should be delivered.
3. Select Feature as a work item type for your dependency and start typing text (name, ID, or tag) in the search box to search for the feature. Click the desired feature to select it.
4. Next to the Requesting option, select Program, and then select the program team that requests the work.

5. From the Requester dropdown menu, select the individual responsible for requesting the dependency.

6. Next to the Depends On option, select Programs, and then select one or more program teams on which your work is dependent.

7. From the Owner dropdown menu, select the individual responsible for responding to the requested dependency.

8. In the Needed By box, use the calendar to select the date this dependency needs to be resolved by.

9. In the Notify field, select one or more individuals that will receive notifications when the dependency is created, committed, or delivered. You can search by first name, last name, or email address in the field. Up to 10 users can be added. External entities can also be added, and the notifications will be sent to the Jira Align owner assigned to the external entity.

10. Click Save. The dependency saves and additional fields display on the Dependency slide-out panel for tracking purposes. The dependency’s originator displays under the Requesting field for further reference.
    When a dependency is saved, the Depends On team is sent an email request to review the dependency. The roles selected under the Program Dependency email setting will receive this email. You can assign links to the dependency that provide more info. After saving, you can also assign stories to indicate the work needed to satisfy the dependency.

At this point, a negotiation takes place between the requester and the respondent. The respondent can access the dependency in the To Do section of the dependencies page and take appropriate action. They can choose to:

• Reject the dependency and provide a reason for the rejection.
• Commit to the Needed By date and accept the dependency.
• Send a new proposed date back to the requester by which the team can deliver the dependency. This can take many iterations until both sides agree on the commit date.

Each party will see a slightly different interface when accessing the dependency in the dependency grid or the dependency panel, depending on the state of the dependency. For example, actions such as accept, reject, or unblock a dependency may be available during the negotiation to commit.

Either party may choose to block the dependency. 

The respondent can also indicate that no work is required for the dependency.

Notes:

• The Depends On team's program room is also updated to include the dependency. The dependencies are listed under Dependency Backlog. You can click the dependency to edit it.
• If the requesting team selects multiple affected teams, for example, if an infrastructure change affects many teams participating in the PI, this will be a multiple team dependency.

Assign items to a dependency

Assigned items are the work items that are responsible for resolving the dependency. These are the features where teams are doing the work needed to remove a blocker. As you plan or adjust delivery, you can use the Assigned items section of a dependency’s details panel to add features that are contributing to unblocking the dependency.