You are the Scrum Master of a team working on a solution that requires a lot of new code and technical facets–more than the usual. Several days into the 10-day sprint, the number of completed story points has not decreased. Overall, things are going fine, but some team members and outside stakeholders are anxious about the apparent lack of progress on the burndown chart. What might you do?
Some teams find burndown charts to be a helpful information radiator. Other teams may not. The charts can also be less helpful when tasks in the backlog are new, uncertain, and difficult to calculate. Looking at velocity (after the fact) may be a better way to work on continuous improvement and planning via estimates.
