10X: Work Tree (Strategy View)

About this report

The Work Tree (Strategy View) report provides an overview of progress on all work items in a selected snapshot (a collection of PIs), as well as a drill-down hierarchy of progress at each work item level. Release train engineers and portfolio managers can use this report to track progress of all work items in a snapshot. Portfolio and company executives can track what work has been allocated against the strategies and are able to see the progress so that they know that the company is progressing towards the strategic commitments they made to the board of directors. 

Generate this report by first selecting a target snapshot from the Snapshot dropdown.

Data on this report can also be shared by creating a screenshot using the Capture button on the top right of the page. This will create an image in a browser pop-up.

Under Extra Configs, use the additional filter options, such as Theme, Theme Group, Epic, Category, or Feature Customers to refine your results. Tags are also available for filtering. You can filter the Work Tree by Release Vehicle and Release Vehicle Group, Sprint, and Product by using the Configuration bar at the top of the page.

With the Show Parent Levels option (only the Strategy view), you can view items above quarterly goals (or any other level the theme is tied to under Administration) to see the full hierarchy of strategy down to stories.

You can also turn on the Bottom-Up option in the Strategy view which builds the hierarchy upwards. The hierarchy is built downwards in a default view.

Prerequisites

  1. PI must exist in the system and be tied to a program. 
  2. Strategic snapshot must be created and tied to a PI. 
  3. Strategies must be created inside the strategic snapshot. 
  4. Themes must be created and tied to a strategy.
  5. Epics must be created and tied to the PI and a theme. 
  6. Features must be created and tied to the Epic. 
  7. Stories, with point values, must be created and tied to features. 
  8. Capabilities are optional (setting must be turned on for the portfolio; will be an additional layer between epics and features), and can be tied epics. 

How are report values calculated? 

Strategy Progress Bar

The progress bar shows the percentage of story points delivered for all PIs in the target snapshot. 

Expandable Drill-Down List/Hierarchy of Work Items

You can also expand each work item in the list to show child work items. For example, expand an epic in the list to see its child features--expand a feature to see a list of child stories. At the story level, click on a story to see details, including acceptance criteria and tasks.

Note: The top level of the expandable drill-down list is set under Administration > Settings > Platform TerminologyCustomize Pyramid Display > Link Theme to.

In the Work Tree, goals are ordered alphabetically. All themes under a theme group are ordered based on the global rank, meaning themes are ordered in the backlog when a portfolio and PI are set to All on the Configuration bar. Epics under themes are also ordered based on the global rank. All other child items are ordered based on the rank under their parent and this order matches the order set in the backlog. For example, capabilities and features are ordered here as they are under an epic in the backlog, features—under an epic or a capability, and stories—under a feature.

At the theme level, you can see a roll-up of the following statistics:

  1. Epic Progress: A progress bar showing the percentage of epics that are accepted for the theme
  2. Feature Progress: A progress bar showing the percentage of features that are accepted for the theme
  3. Story Progress: A progress bar showing the percentage of story points that were delivered for the theme

Columns:

  1. Work Item Name: The name of the work item; click on a work item to open it for editing; icons to the left of the name indicate the state and item type (for example, in-progress epic; hover over the icons to see its tooltip). 
  2. Health: The health of the goal or theme; click the icon palette in this cell to edit the health settings. The column is displayed when the Show Health toggle found in Extra Configs is switched on.
  3. Points: Estimated points pulled from the Story Page/Story panel; the value is a roll-up of all stories tied to the work item 
  4. Items: A count of direct child items for the work item
  5. Progress:  The percentage of story points accepted for the work item; the value is a roll-up of all points tied to the work item 

 Note: Stand-alone features display at the same level as epics.

work_tree_strategy.png

How to interpret this report

Strategy Progress Bars

Compare the Epic, Feature, and Story progress bars, as well as the total story points completed percentages, to see which strategies are lagging behind in completing work items.

Theme-Level Progress Bars

Compare the Epic, Feature, and Story progress bars for each theme tied to a strategy. Ideally, there should be very little lag between story and feature progress. It is not unusual for epics to lag behind even further, because epics span PIs. Pay particular attention to features, to make sure they are not trailing the stories in progress; when feature progress is too far behind story progress, it indicates a prioritization problem for your stories--most likely working on stories for too many features at once. Minimizing the feature work in process allows you to finish individual features before moving on to more stories. In the Backlog, use the Rank Stories by Features option to get a baseline prioritization for stories. A Work in Process Report is also available to help you understand where a bottleneck is impacting feature progress.

Expandable Drill-Down List/Hierarchy of Work Items

Review the progress of strategies, themes, epics, features, stories, and tasks, using the drill-down function in the report, to gain insight into which work items are lagging behind or being completed on schedule. From here, you can also access the work items directly to edit if needed, such as splitting features, prioritizing work items, or reducing scope.

Was this article helpful?
0 out of 0 found this helpful
Print Friendly Version of this pagePrint Get a PDF version of this webpagePDF

Join the Atlassian Community!

The Atlassian Community is a unique, highly collaborative space where customers and Atlassians come together. Ask questions and get answers, start discussions, and collaborate with thousands of other Jira Align customers. Visit the Jira Align Community Collection today.

Need to contact Jira Align Support? Please open a support request.