I am trying to view the burnt down chart using Remaining Estimates, but I am not able to interpret and seeking clarification.
The starting point for the grey line is based on the team's sprint capacity that you would have setup, in this case, seems to be around 65 hours (approximately).
The Red line is the sum of 'original estimates' from all the issues that are part of the sprint, which in this case looks like, far exceed team's capacity. Also, the little dents in the red vertical line is indicative of a sprint planning day, wherein team members were incrementally adding tasks and corresponding original estimates on each of the tasks throughout the day.
Now this is where it gets interesting: the green line is the hours logged by team members on their activities through the sprint, which indicates that the team has the required capacity to deliver the planned work.
This leaves us with one conclusion, that the Team's sprint capacity needs to be increased and ideally, the grey line should be at the same level as where the red line peaks before it trends downwards. Now this conclusion is based on the fact that the red line peaked within a day. If it had peaked over several days, it would have been indicative of scope added after sprint had started and more details would be required to interpret what was going on; but that is for another day.
Hope this helps.
If you already heard about Smart Commits in Bitbucket, know that you just stumbled upon something even better (and smarter!): Genius Commits by Better DevOps Automation for Jira Data Center (+ Server...
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
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events