Overview
Breakdown Views provide a single-pane visual representation of how work is planned and sequenced for Features and PI Objectives across multiple Teams and Agile Release Trains (ARTs). This view solves a common challenge in scaled agile environments: gaining visibility into complex, cross-team work without building complex queries or dashboards.

Breakdown View is a single view of all the work that is planned or unplanned across Teams or ARTs for a Feature or PI Objective.
The problems we solve with Breakdown Views
Imagine, as an RTE or stakeholder, in a steering meeting, you need to quickly visualize the end-to-end delivery of a Feature or PI Objective, cross-ARTs. How do you quickly present this information to the audience?
β
Breakdown Views address several key challenges using the principle of Visual Management:
End-to-End work sequencing: In a single-click, visualize how work items - for a Feature or PI Objective - are scheduled across different Sprints and Iterations. See the planned vs. unplanned work items, the risks and dependencies. Understand how the work is sequenced.
Simplified reporting: Eliminate the need for complex queries and dashboards in ALM tools to visualize cross-Team or cross-ART work item. when Teams and ARTs use different Projects
PI Objective tracking: Visualize, track and govern all the work items, risks and dependencies related to a PI Objective, across Teams, across ARTs.
What you see in the Breakdown View
The Breakdown View displays:
Iterations (Sprints) columns: The Iterations (Sprints) for the PI are displayed as columns. You will see each work item displayed in the Iteration that it is scheduled in, showing the flow of delivery.
Risk and Unplanned columns: Work items that are not yet scheduled in an Iteration are displayed in the Unplanned column. Risks are displayed in the Risk column.
Hierarchical relationships: All parent and child work items that are linked to either the Feature or PI Objective are displayed. It is an end-to-end visualization of the work items related to the two primary work items (Features and PI Objectives) that are managed in a PI. Breakdown Views support the practice of Systems Thinking!
ARTs/Teams as swimlanes: Quickly visualize how work is distributed across different Teams and ARTs. Multiple Teams/ARTs will work on the same Feature or PI Objectives. Now you can easily coordinate and manage this cross-Team and cross-ART coordination.
How to access Breakdown Views
You can open a Breakdown View from two locations:
From a Feature sticky note: Click the Breakdown toolbar icon on any Feature card
From the PI Objectives page: Access the Breakdown View for any PI Objective
From a Dependency sticky note: Click the Breakdown toolbar icon on a Dependency.
From any Links chip pop-up modal: Click the Breakdown button on any Feature, Dependency or PI Objective.
Breakdown View accessible from the ART PI Objectives or Team PI Objectives page.
Breakdown View accessible from the Feature or Dependency Sticky Note toolbar.
Breakdown View accessible from the Links chip pop-up modal on a Feature, Dependency or PI Objective.
When/How to use Breakdown Views
Breakdown Views are particularly valuable for:
Solution Train or ART stakeholders - who need to understand the end-to-end work scheduled for Features or PI Objectives instantly in steering meetings
Planning sessions - where you need to see and discuss the full scope of a Feature or PI Objective
Execution Mode - easily monitor and govern progress across multiple Teams/ARTs
Identifying gaps - in work scheduling or unplanned work that needs attention
Key Benefits
Making Work Visible: a single click and view to see all the planned and unplanned work, risks and dependencies associated with Features and PI Objectives. No more guessing.
No configuration required: Automatically available in all PI sessions. One-click access to comprehensive work visualization
Works across Teams/ARTs: Remove the chaos queries and filters present in ALM tools to get an end-to-end view.
Unique for PI Objectives: A visual capability not typically available in standard ALM tools to steer and govern the outcomes of the PI via PI Objectives.
Cross-Function and Cross-Domain Visibility: across teams, ARTs, External Orgs and the PI time horizon.
Enhanced Decision Making Support:
Apply Systems Thinking principles in real-time
Identify bottlenecks and impediments to the flow of work
Reduce cycle time through better visibility
Reduce the risk of items not being delivered (completed) on time



