jirascrumjira-agileburndowncharts

Scrum - Burndown - What happend when the remaing hours is 0 but the story is not finished


I'm new on Scrum, and I have a question about Burndown chart.

Where I work, we use the burndown chart with remaining hours (not points), so I have a question about what to do when a task consume all the estimate hours but it is not finished.

For ex: an story was estimated with 10 hours, but the team already used 10 or 12 o 20hrs so Jira shows as remaining hours 0 (it shows cero once the spent time is equal or higher than the estimated) The issue is that when I build the Burndown, the story said that the remaining is cero, so it looks like the story was finished, but that could not be the real status. How can I reflect that in the Burndown?


Solution

  • In Jira, when you are logging your time spent for the day just add how many hours you think it would take to complete the work to the remaining work field. The original estimate will remain the same, the remaining estimate will update to what you set it to. The original estimate bar will show the change in scope showing the additional scope as an extended grey bar to the right of the green bar.

    From a project managers or a team leads point of view you should bring this up with them at the next stand-up meeting or immediately ask that question of them so they can plan appropriately.