Why Cross-ART Dependencies
Cross ART dependencies in the SAFe are critical, inter-team constraints where one Agile Release Train (ART) requires capabilities, features, or architectural components from another ART, to deliver a large-scale solution.
These dependencies are managed primarily through PI Planning, the Solution Train, and ART Sync events. piplanning.io will help you visualize and manage cross ART dependencies to prevent bottlenecks, ensure, alignment, and reduce risks that occur when cross ART dependencies are not proactively managed.
Managing these types of dependencies during PI Planning Events and tracking them during PI Execution is essential to avoid misalignment, delays, and duplicate planning efforts.
Key Aspects of Cross ART Dependencies
Definition: Situations where the output of one ART is a necessary input for another.
Occurrence: Highly common in large solutions (Solution Trains) where multiple ARTs work together.
Impact: Unmanaged dependencies lead to missed PI objectives, delayed delivery, and reduced flow of value.
piplanning.io is designed to uniquely manage Cross ART dependencies using the Dependency Sticky Note function. Using the normal Dependency Sticky Note behaviors, you can immediately and automatically visualize and manage cross ART Dependencies with minimal overhead.
Are you new to the Dependency Sticky Note function/type? Start with The Dependency Management Flow to understand the basics first.
Creating, sharing and resolving Cross ART Dependencies
Follow these steps to create, share and visualize a cross ART dependency sticky note on the Team and ART/Solution Planning Boards:
NOTE: After this flow, the Dependency Sticky Note will be visualized on both Team Boards and both ART Planning Boards of the involved Teams.
Create a Dependency Sticky Note on your Team Board in the Iteration when you expect the delivery.
Optional: Link the Dependency to the related Feature. The link potentially ensures clear visual context for the Team you share the Dependency with.
Share the Dependency to the delivering Team. Use the "Depend" button on the sticky note action bar or the "Depend On" chip directly on the sticky note to share the dependency to the team you're relying on.
To share a Dependency Sticky Note with a Team in a different ART, go first to Other ARTs, select an ART and a Team within that ART.
Have the needed conversation with the delivering team on how and when they plan to get the dependency solved.
IMPORTANT: Make sure that the work of the delivering team is linked to the Dependency as well as to the Feature (This will be used to track the work on the Feature and Dependency)
Once agreed on a plan, both Teams Mirror the Dependency Sticky Note on their ART Planning Board
Optional for the requesting Team: If you haven't already linked the Dependency Sticky Note with the Feature in Step 2, now link the Dependency to the related Feature directly on your ART Planning Board.
Remove the Red Flag to indicate that both Teams agreed on the Dependency.
When the flow is done, the Dependency is visualized on both Team Board (Requesting and Delivering Team) and on both ART Planning Boards.
ART Planning Board - Requesting Team
ART Planning Board - Delivering Team
Visualize Dependencies on the Solution Planning Board
Cross-ART Dependencies can be visualized on the Solution Planning Board.
Note
You may not want to mirror all cross-ART Dependencies on the Solution Planning Board, but focus on the most important / relevant ones.
Once a Dependency is mirrored onto the ART Planning Board follow these steps to mirror the Dependency on the Solution Planning Board.
Select the Dependency on the ART Planning Board
Click the "Mirror" button
Select Solution Planning Board
Then the Dependency will be visualized on the Solution Planning Board in the corresponding ART Swimlane.