Targetprocess: Define and Communicate Dependencies

Product Managers, Product Owners, and Scrum Coaches can add dependencies on other teams directly into Targetprocess but also must communicate with the team whose time is being requested to negotiate and coordinate work. 

• In the weeks before PI Planning starts, as Features are defined, Product Managers should communicate about expected Dependencies. 
• During PI Planning, teams should be in contact about timing and expectations for dependent work. 
• If Dependencies change after PI Planning, teams must renegotiate and communicate with the appropriate teams, Product Owner, and Product Manager.

In this article:

• Understanding dependencies
• Defining a dependency between teams in the same ART
• Defining a dependency between teams in different ARTs
• Using the ART planning board

Understanding dependencies

When one team's work relies on work from another team at any point, this is called a dependency. For example, Team 1 has a Feature that includes work that must be completed by Team 2. In this case, Team 1 is dependent on Team 2, so Team 2 would have one or more Stories associated with Team 1's Feature. 

Note: For work that must happen in a certain order, refer to Define Time-Based Dependencies Between Stories and Between Features.

Defining a dependency between teams in the same ART

Dependencies can be entered as Stories that are associated with a Feature. 

1. Create a Story for the dependency.
2. Expand the Assignments section of the Story and associate it with the appropriate team.
   1. If the original team is already assigned to the story, select the red X to remove the team.
   2. Select the green + next to Teams.
   3. Choose the appropriate team from the list.
      • Dependencies on outside vendors, contractors, or groups who are not in any ART can be assigned to the Vendor, Contractor, & External team for your team's ART.
3. Specify the Iteration, if known:
   1. Expand the Info section.
   2. Ensure the Story is associated with the correct Feature.
   3. Mouse over the area to the right of Team Iteration and select Edit (pencil icon).
   4. Select the appropriate Iteration.

Note: Dependencies that you assign to other teams will not appear on your Team Backlog. To see dependencies that you assign to other teams, refer to Targetprocess: View Dependencies between Teams and ARTs. 

Defining a dependency between teams in different ARTs

1. From any view, select the global + Add button in the upper-left.
2. Ensure Story is selected from the list of entity types on the left. 
3. Name the Story, select your own team from the Teams drop-down, and select Add & Open. 
   1. Do NOT add a Feature or a Planning Interval at this point.
   2. If needed, select the appropriate Portfolio.
4. Expand the Assignments section, remove your team, and add the dependent team.
5. Expand the Info section and add the appropriate Feature.
6. Add clarifying comments for the dependent team in the Description tab.

Using the ART Planning Board 

The ART Planning Board is a useful view for creating dependencies because you can see both teams and the dependent work at the same time.

Showing relationship connectors and hiding empty views

When using the ART Planning Board, make sure to show relationship connectors (lines connecting dependent Stories and Features across teams), and hide empty views so you can focus on the dependencies.

1. In the navigation menu, expand the ARTs folder
2. Expand the PI Planning subfolder
3. Select ART Planning Board
   1. Select the Actions menu in the upper right.
      1. Select Visible next to Empty Lanes (to toggle this setting to Hidden).
      2. Select Show next to Relations.

Refer to View Dependencies between Teams and ARTs for more details.