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.

Dependencies can be viewed in a variety of places.

You are viewing: What Does The Art Planning Board Show

Read more : What Is Constructive Fraud

In this article:

• Viewing dependencies assigned to a specific team
• Viewing dependencies between ARTs
• Viewing dependencies between teams

Viewing dependencies assigned to a specific team

Most of the team-focused views in Targetprocess will show Stories, Bugs, or Features that have dependency relationships with other teams. For example, if a dependent Story is assigned to Team 2, but the associated Feature belongs to Team 1, the following views will be useful:

• Team Backlog
  • When filtered to Team 1, shows Team 1’s Feature and only the Stories assigned to Team 1 (in addition to Team 1’s other Features and Stories).
  • When filtered to Team 2, shows Team 1’s Feature but only the Story assigned to Team 2 (in addition to Team 2’s other Features and Stories).
• Team Kanban, Team Iterations, and Iteration Planning
  • When filtered to Team 1, shows the Stories assigned to Team 1 (in addition to Team 1’s other Stories).
  • When filtered to Team 2, shows the Story assigned to Team 2 from Team 1’s Feature (in addition to Team 1’s other Stories).

Read more : What Does Conditional Absolution Mean

Navigate to any of these views by expanding Teams, then Team Overview from the left navigation menu.

Viewing dependencies between ARTs

The ART Planning Board makes it easy to see dependencies between teams on the same ART and between different ARTs. This board shows all Features for the team(s) defined by the Portfolio, Agile Release Train, Program Increment, and/or Team filter, AND all dependent Stories, Bugs, and Features assigned to other teams.

1. Navigate to ART Planning Board.
   • Expand ARTs, then PI Planning, then select ART Planning Board from the left navigation menu.
2. Filter by the appropriate Portfolio, Agile Release Train or Teams, and Program Increment, if desired.
   1. Refer to Filtering the Content of a View or Folder for instructions.
   2. See filter settings for specific use cases below.
3. If necessary, ensure empty columns are hidden:
   • Verify the Click to see hidden empty lanes icon displays in the upper right.
   • If the icon is not showing:
     1. Select the Actions menu in the upper right
     2. Select Visible next to Empty Lanes (to toggle this setting to Hidden).
     3. Select outside the Actions menu to close it.
4. If necessary, show relationship connectors (lines connecting dependent Stories and Features across teams):
   1. Select the Actions menu in the upper right.
   2. Select Show next to Relations and ensure all check boxes are checked.
   3. Select outside the Actions menu to close it.
5. View the dependencies between teams:
   1. Green or blue solid connecting arrows between Stories and/or Features indicate dependencies that have been planned to complete in a logical order.
   2. Red dashed connecting arrows indicate problems with the plan, for instance, when a dependent Story is planned for the iteration after the Feature should be complete.
6. Adjust dependencies if needed:
   • Select and drag a Feature or Story to show which Team is primarily responsible and the Team Iteration in which it is planned to be completed.
   • As always, communicate with other teams about the timing and other specifics of dependent work.

Viewing dependencies between teams

The Team Planning Board focuses on Stories and Bugs. It shows all Stories and Bugs for the team(s) defined by the Portfolio, Agile Release Train, Program Increment, and/or Team filter, AND all dependent Stories and Bugs assigned to other teams. The Team Planning Board is most useful for viewing time-based dependencies, since it does not display Features.

1. Navigate to Team Planning Board.
   • Expand ARTs, then PI Planning, then select Team Planning Board from the left navigation menu.
2. Filter by the appropriate Portfolio, Agile Release Train, Program Increment, or Teams if desired.
   1. Refer to Filtering the Content of a View or Folder for instructions.
   2. See filter settings for specific use cases below.
3. If necessary, ensure empty columns are hidden:
   • Verify the Click to see hidden empty lanes icon displays in the upper right.
   • If the icon is not showing:
     1. Select the Actions menu in the upper right
     2. Select Visible next to Empty Lanes (to toggle this setting to Hidden).
     3. Select outside the Actions menu to close it.
4. If necessary, show relationship connectors (lines connecting dependent Stories and Features across teams):
   1. Select the Actions menu in the upper right.
   2. Select Show next to Relations and ensure all check boxes are checked.
   3. Select outside the Actions menu to close it.
5. View the dependencies between teams:
   1. Blue solid connecting arrows between Stories/Bugs indicate dependencies that have been planned to complete in a logical order.
   2. Red dashed connecting arrows indicate problems with the plan, for instance, when two Stories need to take place in chronological order, but the first Story is planned for the iteration after the second Story should be complete.
6. Adjust dependencies if needed:
   • Select and drag a Story or Bug to show which Team is primarily responsible and the Team Iteration in which it is planned to be completed.
   • As always, communicate with other teams about the timing and other specifics of dependent work.

Source: https://t-tees.com
Category: WHAT