Sprint burn down report not helpful

[Glenn Butler]

Hello,

Our SDLC has definition of done when it passes QA approval and the ticket is "Ready For Stage".  Since the sprint report out of the box appears to be "Closed" this does not happen until the last steps of our SDLC which involves external departments (security, etc).  Thus all of our burndown reports have a RED line for "Closed" that never decrements until the very end of our sprint.  

I"m wondering if we are doing something wrong, because "done" will never occur until the very end, therefore burndown is not helpful. Is there a way to track the another metric such as "ready for stage"?

glenn.

[Mark Segall · Accepted solution]

Hi @Glenn Butler and welcome to the community!  The most important thing to understand about the sprint report is that it's a reflection on your immediate scrum team.  Outside factors should not play into your burndown.

With this said, I would separate the activities into separate linked issues.  For example, the story would be "Done" when the developer/QA work is complete.  From there you could have a TASK for Security or other groups to perform their final review on the broader sprint backlog.  If anything is identified during this final phase, you would just create new linked issues accordingly.  This would give you a true representation of velocity on your sprint report and separate out things that are not under the scrum team's span of control.