Amber Hunt - Sprint 4 Paper 2 - Burning down the sprint

Introduction

Burning down the sprint can be challenging especially if it’s the teams first time doing an agile project. In agile, the more things are done, the better. Eventually, the team becomes use to doing it and gets faster at it. Posting the sprint burndown chart and updating the burndown are tools that can help with “burning down the sprint”. These guidelines are very helpful and simple to follow.

  Posting the sprint burndown chart

Burndown charts shows work the team has to complete and the work they already completed. They are transparent and easy to read graphic presentations. (Lynda.com – from LinkedIn, 2017) Here are two types of burndown charts, they are release and sprint burndown. They both have charts and are easy to read. But the only thing is, these charts cannot expand past the due date. '''Updating the burndown            Updating the burndown is very simple. If the team has a certain velocity, it is expected to meet that number of stories in every sprint. Every time there is a standup, the scrum master must add to the finished stories. A “dot” is then placed on the burndown that matches the completed stories. (Lynda.com – from LinkedIn, 2017)

Conclusion

All-in-all, burning down the sprint is relatively simple. One these instructions are followed, it can be done. With posting the sprint burndown chart, two choices of charts can be picked, but they’re similar. These charts help to see what the team has and has not done. Updating the burndown helps set the pace. It can either be very fast, or very slow. All-in-all, these tools can help with “burning down the sprint”.