I was wondering if it possible to track the burndown of story points before a story is completed. (Somewhat similar to burning down hours in team which estimate by hours).
No, it's not.
Jira Software sticks to the full scrum committment and definition of done - either an item you committed to is done, or it is not. There is no partially done, it's a binary flag. You only burn-down on items that are done.
There are plenty of good reasons to be able to see progress, but they're not burn-down (because the committed items must be done to burn down), and Jira is weak on reporting that.
Clear, thank you Nic.
We are struggling with this ourselves. We want to see points burn down through the sprint. But DONE means that it's been accepted at the demo ceremony at the end of the sprint by our Product Owner. That makes our burndown chart pretty useless through the course of the sprint. I should note we release every sprint as well, so our version reports don't really work either in this model. Any suggestions are appreciated!
That's not supported. In Scrum, it's not up to the product owner to say something is done (although they certainly should be defining the definition of done for them!), and it's certainly not done at the demo ceremony. You mark things done when the developers (and testers if you've included them in the dev team and process) say it matches the definition of done, during the sprint.
It's fine to work differently of course, but for your case, you've gone a way outside the normal definition of Scrum, far enough that Jira doesn't support it.
It looks like you're new here. Sign in or register to get started.
