Skip to main content

Handling Critical and Risky Cross-Team and Cross-ART Dependency Warnings

Attention RTEs: Handle Critical and Risky Cross-Team and Cross-ART Dependency warnings in real time with zero overhead and effort via the Risk Links quick filter.

If you encounter a dependency that doesn't align with your timeline, you'll see an alert in the top navigation and warnings visualized on the boards.

Warning Notification

An alert appears in the top-right navigation in case one or more links/dependencies on a board are in a risky or critical state. The icon is called Risky Links and appears as the red and amber circle icons as seen below.

Risky Links icon in the top right navigation of the ART Planning and Team Boards

When you click on the Risky Links alert this automatically filters the board by highlighting the corresponding Dependency and Work Item sticky notes that are not aligned on the schedule, causing significant risk to the PI plan.

ART Planning Board displaying critical or risk links related to planned Dependencies


When clicking on the Risky Links icon you enter into Search mode.

  • Toggle between Critical or Risky links depending on your focus

  • Use the Risky Links filter in combination with other search criteria to find the information you need to solve a scheduling issue, make trade-off decisions or answer any question from the SoS or management stakeholder ceremonies

Search mode on the ART Planning Board and using the Risky Links filter


Risky Links Warning States

Risky

The link might be achievable by the implementing team, but there's a significant risk involved. This warning is triggered when the dependency is scheduled for the same sprint as its corresponding Feature (program level item).

Critical

The link isn't feasible within the set timeline. Specifically, this warning appears when the feature (which relies on this dependency) is slated for delivery before the dependency itself is complete.

Dependency Warnings on the Team Board

On the Team Board, stickies that are linked to a Dependency will spotlight Critical dependencies, particularly when the team-level sticky is set for implementation prior to the scheduled completion of the dependency.

Did this answer your question?