At a Glance
Who it's for: Everyone. RTEs, Program Managers, Enterprise Architects, Scrum Masters, Product Management, Team Leads, Team Members and Stakeholders.
Where to find it: The Map icon on any Sticky Note toolbar, or on any ART or Team PI Objective.
What the Map Shows
At scale, it is hard to see how all planned work fits together. The Map connects tangible work (Backlog Items) with intangible work (Goal Setting, PI Objectives, Outcomes, Risks, Dependencies and Notes).
Title Bar: shows Map and the name of the artifact that you opened it from.
Click X at the top right to close.
Search: for an an item on the Map using keyword search.
Assignees: Filter by Assignee.
Type: filter by specific artifacts or item types.
Group by: arrange items into Rows and Columns (see below).
Plan and Execution Mode: toggle between Plan Mode and Execution Mode.
Map of This Item: the label on the item you opened the Map from.
Lines: the links between related items. Work reads left to right, from Portfolio Initiatives, and ART or Team PI Objectives, to Features and Dependencies, to Stories and Risks.
Zoom: − and + at the bottom right zoom out and in. The circular arrow resets the view.
The Map is view-only. It shows what has been planned, and it does not change the plan.
How to Open the Map
From a Sticky Note:
Click on a Sticky Note on any Board.
In the Sticky Note Toolbar, click the Map icon.
From a PI Objective:
Open the ART PI Objectives or Team PI Objectives panel.
On the PI Objective you want to explore, click the Map icon.
Result: The Map opens for the selected Sticky Note or PI Objective.
How to Group the Work
On the Map, click Group by.
Turn on Group items.
Under Rows, select ART, Team, Iteration, Objective or Status.
Under Columns, select a different option from the same list.
To swap Rows and Columns, click the ↔ arrows between them.
Result: The Map arranges the work into a grid. With Team × Iteration, each Team gets a row and each Sprint gets a column, plus columns for the IP Sprint and Risks. Items without a Team or Iteration, such as PI Objectives and Milestones, sit to the left of the grid.
Note: The Map feature replaces Breakdown Views, which will be phased out. The phase-out date will be announced.
Coach's Corner
Systems Thinking meets Visual Management: end-to-end views of any item planned in the PI. Understand context, relationships, and the planned delivery schedule in a single view. Bring clarity to your conversations.
When to Use the Map Use it in any event where people need the same picture of the plan: the PI Planning Event, Scrum of Scrums, Management and Stakeholder Syncs, Inspect & Adapt, Portfolio Reviews, Sprint Planning, Retrospectives and Management Forecasts.
Cross-ART and Cross-Team Schedules Group by Team × Iteration to check that everyone agrees on when each piece of work lands. A Story scheduled after the Feature it supports, or a Dependency in a later Sprint than the work that needs it, becomes visible immediately.
Steering by PI Objectives and Outcomes Open the Map from an ART PI Objective to see every Team that contributes to it. In a Management Sync, this shows you which Team to ask about which Outcome.
Facilitator Tip Share your screen with the Map open instead of reading out status lists. Everyone then discusses the same view of the plan.
Questions
Can I edit work on the Map? No. The Map is view-only.
Does the Map update Jira Software, Azure DevOps or Rally Software? No. It does not read from or write to your ALM tool.
Does an Admin need to turn it on? No. The Map feature is on by default for everyone.
Related Articles