Hello, Could someone please help me with more details and how to implement the following reports: ART * Feature cycle time across the Program Kanban reporting * Program Predictability – setting up objectives, tracking and accepting, then running the progress by objective report Delivery Teams * Story burn up and burn down * Cumulative flow diagram from Implementing to Staging Is there a better view/report of feature commitment to completion (full feature vs. individual team work) ? Thank you.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Help with Reporting

Reddy_fnd6qb

Hello,

Could someone please help me with more details and how to implement the following reports:

ART

Feature cycle time across the Program Kanban reporting
Program Predictability – setting up objectives, tracking and accepting, then running the progress by objective report

Delivery Teams

Story burn up and burn down
Cumulative flow diagram from Implementing to Staging

Is there a better view/report of feature commitment to completion (full feature vs. individual team work) ?

Thank you.

Accepted answers

Tina Behers_cd5uzj

re: features committed v completed - I would suggest the PI Scope change report -

Program -> Planning Increments-> More Actions -> Scope change report

PS - Pro -Tip - under the same menu is the PI Close report - this provides a centralized view of all items put into the PI that have not yet been accepted (before the end of the PI)

All comments

Reddy_fnd6qb

Could someone kindly provide some insight on my requests above?

Tom O_Connor

ART

Cycle Time - this does require you setup process steps for the Features. https://agilecrafthelp.zendesk.com/hc/en-us/articles/115001314774-10X-Process-Step-Cycle-Time.
Program Predictability - this is based on Program Objectives and setting the Planned Value and then the Delivered Value over the PI. https://agilecrafthelp.zendesk.com/hc/en-us/articles/115004944748-10X-Progress-by-Objective

Delivery Teams

Story burn ups does require some setup as described in the report. Essentially all stories should be sized and tied to features in the PI. https://agilecrafthelp.zendesk.com/hc/en-us/articles/115002873287-10X-Program-Increment-Burnup-by-Story
https://agilecrafthelp.zendesk.com/hc/en-us/articles/115001386093-10X-Team-Burndowns
Cumulative Flow - https://agilecrafthelp.zendesk.com/hc/en-us/articles/115005258428-10X-Work-In-Process-by-State

Reddy_fnd6qb

Hello @Tom O_Connor ,

Thank you very much for your help. Could you also please suggest on 'Is there a better view/report of feature commitment to completion (full feature vs. individual team work)?'

If a feature has stories with multiple teams(18 teams) working on each story, it is really difficult to track the status of the feature in the program board. I'm wondering if there is a better way to view/report of feature commitment.

Thank you.

Tom O_Connor

You might look at the Work Tree view to track progress of the feature and it's stories across the teams.

Reddy_fnd6qb

I did look at the work tree but it is similar to that of feature panel view. It doesn't display team names beside stories. I'm wondering if there is any other report that could display better.

Thank you.

Tina Behers_cd5uzj

re: features committed v completed - I would suggest the PI Scope change report -

Program -> Planning Increments-> More Actions -> Scope change report

PS - Pro -Tip - under the same menu is the PI Close report - this provides a centralized view of all items put into the PI that have not yet been accepted (before the end of the PI)