Help with Reporting
Asked by Reddy:

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.


Answers:
author: Tina Behers
body: 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)


author: Tom O'Connor
body: 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.](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>

comments: author: Reddy
body: Hello [@Tom O_Connor](/t5/user/viewprofilepage/user-id/3078478) ,

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.


author: Tom O'Connor
body: You might look at the Work Tree view to track progress of the feature and it's stories across the teams.


author: Reddy
body: 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.


author: Tom O'Connor
body: Maybe I'm not understanding what you are looking for exactly. Have a look at Feature Backlog-\>Kanban-\>State View and select the three dots to show features by team by state. ![Screen Shot 2020-06-03 at 9.34.43 AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/97582i5A065C54DF293FAD/image-size/large?v=v2&px=999 "Screen Shot 2020-06-03 at 9.34.43 AM.png")![Screen Shot 2020-06-03 at 9.34.57 AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/97581iBF4922561B881533/image-size/large?v=v2&px=999 "Screen Shot 2020-06-03 at 9.34.57 AM.png")


author: Reddy
body: Could someone kindly provide some insight on my requests above?