We are using time to estimate our work as we bill by the hour and run weekly sprints
I am looking at a burndown chart where we track time spent using remaining time estimate as I want to understand it better as to give feedback to the team
My understanding is:
Screenshot of Velocity Report
Thanks for all your help - I know it's a month full
The green line is the amount of effort in the sprint i.e. the amount of time that has been logged by the team. If an item is taken out of the sprint, the time that was logged on that item doesn't relate to the sprint anymore, hence it will go down slightly.
The red line is the remaining time, which will change when :
I don't see any attachment here, but from your Burndown description, the difference between commitment and remaining ISN'T necessarily the scope change - it would only be that if it was a perfect situation where each team member logged exactly 1 day's hours every day and never updated a remaining estimate.
Under the Burndown chart is the list of all sprint changes and that is the only accurate log of scope changes.
Thanks for the feedback. I will attach the screenshots again as a reference
(Which was suppose to be attached)
I am still a bit unclear as to why the green line burns down if an issue was removed. My take on the green line is time logged during the sprint, so why would it burn down? To me, that drop shows time not logged (Losing an hour's logged work)
There is also a discrepancy between the Velocity Chart and the burndown as per the screens shots. Any idea why this is?
Velocity Report: 343.48h
Velocity Report: 204.43h
The green line is time logged "in the sprint", so if you take something out the sprint, it then doesn't count as part of that sprint (or at least that's my reasoning).
Honestly, I'm not a fan of Jira's Velocity report. I wonder if the velocity is based on Original Estimate, as opposed to Remaining Time, that could explain the discrepancy
Think I will do some investigations and see what the discrepancy is between the 2.
I agree that the time is logged "in sprint", but I don't see the reasoning behind the greenline burning down if it's removed from sprint. Almost seems like the team is being penalised with the remaining estimate if it's removed for whatever reason. I will do some testing here also to see what the behaviour would be for a task that gets removed with no remaining estimate.
Thanks for all your help
When to use CSV importer When managing your processes in Jira, there are many occasions where you need to create a lot of tasks. Creating them one by one will cost you a lot of time and effort and i...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event