This question is locked. New answers and comments are not allowed.
In the latest update I see that there is now a traditional burn-down graph based on hours of work remaining. That's helpful but we would like to see that style of burn-down added to the dashboard.
More background.
The concept of using story points for burn-down seems unique to Telerik. We can find no other examples of it on the Internet in the SCRUM community anyway. For a lot of Agile teams, sprints involve only a few stories - sometimes only 1 - per iteration. With the Telerik dashboard burn-down chart, you see no progress until the story is complete and marked done. The idea behind a burndown is to track progress for the team and client project managers. On our 3-week sprints containing one or two stories, we see no progress at all until the last couple of days of the sprint when the stories are completed. Are others finding burn-downs based on story points useful? Are we just old school Agile?
Thanks
More background.
The concept of using story points for burn-down seems unique to Telerik. We can find no other examples of it on the Internet in the SCRUM community anyway. For a lot of Agile teams, sprints involve only a few stories - sometimes only 1 - per iteration. With the Telerik dashboard burn-down chart, you see no progress until the story is complete and marked done. The idea behind a burndown is to track progress for the team and client project managers. On our 3-week sprints containing one or two stories, we see no progress at all until the last couple of days of the sprint when the stories are completed. Are others finding burn-downs based on story points useful? Are we just old school Agile?
Thanks