Burndown / burnup

[Jon Radin]

I want to create a sprint burndown/burnup report.  We just implemented scrum boards and are not using "story points" (using hours).  Can I still build a report?  If so, I do not see an option on the Reports tab.

[Trudy Claspill · Accepted solution]

Hello @Jon Radin 

Welcome to the community.

Are you working with a Company Managed or Team Managed project? It will say at the bottom of the navigation pane on the left?

And can you confirm it is a Software project? "Software" will display at the top of the navigation pane, below the project name.

For both Company Managed and Team Managed projects with Scrum boards there are built in BurnUp and BurnDown charts under the Reports option (in the Navigation pane). Both reports allow you to display the data in story points or in hours/time. If you are not seeing that, please provide a screen image of what you see.

[Jon Radin]

Trudy...thanks for your quick response.  To answer your Q's:  It is company managed and a software project.  We are using hours/time.  I now see the "burn" charts.   So my next question is:  Am I correct that the status of "Done" is what is used to mark an issues/task completed against the outstanding work?

Regards, JR

[Trudy Claspill]

Issues are determined to be "done" for these charts not simply based on their Status. "done" issues are those for which their Status is mapped to the column farthest to the right on your scrum board. And you can have multiple statuses mapped to a column.

For instance you have a Status named "Done" and a Status named "Cancelled". Both of these Statuses are valid end points for an issue. At the end of your sprint you want issues in both of these statuses to be considered "done".  You will need to map both of these statuses to the right-most column on your board for the issues in both statuses to be considered "done" and included in the burndown/up charts.

If instead you mapped them to different columns, for instance one for Done and one for Cancelled, only the ones in the right-most column would be considered "done". The ones in all the other columns are considered "not done" and not included in burndown/up charts. Those "not-done" issue will also be transferred to the backlog (or another sprint, at your discretion) when you close out your active sprint, because they are "not done".

[Jon Radin]

thanks again Trudy.  I read-up on some similar questions and see that I might not be the only one who defines development work as "done" but still want to track testing/release which may fall into a subsequent sprint.  Any thoughts?   

As background, I primarily want to track our developer work and be able to use burn down/up reports to track progress.  Once finished and in UAT that gets tracked separately as some release builds take more than one sprint.  I do not want to lose track of UAT work as if there is a fail and re-work, that would be included in the current sprint.

Recommendations appreciated...as are the the timely responses you folks provide.

Regards, JR

[Trudy Claspill]

I recommend that you open a new post on the topic of tracking completion of developer work separately from UAT, so that others will see the post topic and comment on it. This post originally has a different topic and is marked as Answer Accepted, so community members are less likely to look at it to see if additional questions have been posted in it.

To answer your question though, in my opinion you have to decide what it really means for the work to be "done". If testing finds a problem, is the original story going to be reopened or is a new story going to be created? If the original story is reopened, then in my opinion the work is not "done" until testing is also done.

If you really want to track the completion of development (prior to testing) separately from the testing activities, then I would recommend that you create separate stories for tracking the testing activities, and link those to the corresponding development story. Then development and testing activities each have a workflow from To Do to Done that they follow, and the backlog and completed work for each type of activity can be tracked and visualized in Burndown/up charts.

[Jon Radin]

I will investigate the separate "testing story" option.

Thanks, JR