Search Sort Posts:  Oldest to newest Newest to oldest

02-15-2010, 10:11 Russweb Joined on 02-12-2010 Posts 10 Sprint Burndown Report - Contains work not in sprint. 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?    Report

02-16-2010, 6:24 Crispin Parker Joined on 11-13-2007 Posts 977 Re: Sprint Burndown Report - Contains work not in sprint. 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"    Report

02-16-2010, 6:37 Russweb Joined on 02-12-2010 Posts 10 Re: Sprint Burndown Report - Contains work not in sprint. 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?    Report

02-23-2010, 4:06 Steve Wright Joined on 02-05-2008 Egham Posts 173 Re: Sprint Burndown Report - Contains work not in sprint. Hi 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    Report

Scrum for Team ... » Version 3.x - T... » Scrum for Team ... » Re: Sprint Burndown Report - Contains work not in sprint.

(please select) Forums Home |- Search Forums |- Active Topics |- Unanswered Posts User Options |- Sign In |- Join this community |- Forgot Password Scrum for Team System |- Scrum for Team System - Announcements |- Scrum for Team System - Feature Suggestions |- Scrum Guidance Version 3.x - Team Foundation Server 2010 |- Scrum for Team System - V3 RC Discussions |- Scrum for Team System - V3.x Beta 2 Discussions Version 2.x - Team Foundation Server 2008 |- Scrum for Team System - v2.x Discussions |- Engineering Practices – v2.2 Reports Version 1.2 - Team Foundation Server 2005 |- Scrum for Team System - v1.x Discusions Task Board for Team System |- Task Board for Team System - Discussions |- Task Board for Team System Beta Discussions (Read Only)