Recently, I was discussing our burndown capabilities within VersionOne. A prospect was providing me some information about their workflow and how they create their stories. Their team does task out stories, but they don’t assign hours to those tasks. They prefer to get their stories as small as possible and burn down directly from those story points.
Due to this, the Sprint burndown chart was not showing any information. For our Sprint burndown chart to show data, we need remaining hours on a task. As stories are closed out and the hours left “To Do” are decreased, the burndown chart plots this. However, in the case of no hours, what’s a ScrumMaster to do? (Pun intended!)
VersionOne Reporting comes to the rescue here. One of the many reports we offer is a Project level burndown chart. Within that report, one of the filters you can choose is a particular sprint. By focusing on that one sprint, you can get a story point burndown chart. So, if your organization breaks down stories into tasks and tests but only to serve as reminders, then the Project level burndown chart is your friend. Couple this together with VersionOne’s ability to track estimate at the story level, task level or both, and you can see how we let organizations do agile their way!
Happy agile, everyone!