Re: Sprint Burndown Report - Contains work not in sprint.

Scrum for Team System - V3.x Beta 2 Discussions

Sprint Burndown Report - Contains work not in sprint.

Russweb 02-15-2010, 10:11
All,
We were comparing a "All Work Remaining in the Sprint" type query with the Sprint Burndown report that came with the template.
The Burndown report shows a TON more work than is actually remaining for all Open Tasks in the Sprint.
When I drilled into the report, I found that it still is factoring in a lot of Tasks that were rescoped or descoped from the Sprint along time ago.
Why is it still including these?

Re: Sprint Burndown Report - Contains work not in sprint.

Crispin Parker 02-16-2010, 6:24
Have you read this blog post?

http://consultingblogs.emc.com/simonbennett/archive/2010/01/22/descoping-work-in-scrum-for-team-system-version-3-0.aspx

It talks about how to change scope while sprinting.

Regards,

Crispin Parker,
Senior Practice Consultant,
EMC Consulting.

"It is better to light a candle than to curse the darkness"

Re: Sprint Burndown Report - Contains work not in sprint.

Russweb 02-16-2010, 6:37
Absolutely.
Great article. Solved some other questions we had.
However, it doesnt solve the problem I'm seeing with the sprint burndown report.
For example I drill into the report to see which items it is listing to make up the "work remaining" it is showing. Some items where both the PBI and the associated SBTs have been moved out of the sprint are still part of the data.
This results in an incorrect burndown.
What could I be missing?

Re: Sprint Burndown Report - Contains work not in sprint.

Steve Wright 02-23-2010, 4:06

The burn down report needs to have all product backlog items within a team sprint save with the status of descoped first, which should also update the associated sprint backlog task as long as the event service is running. Then product backlog items can be move out of the team sprint, but this action not need for the report to show that work has been descoped within the team sprint.

To help fix your burndown I would recommend the following:

Move the sprint tasks, which were descoped, planning scope back to the assign to team sprint, and if not already set the status to descoped, save the changes
Afterwards move sprint tasks planning scope back to the associated product backlog item level

Regards

Steve Wright
Technical Consultant
EMC Consulting