Scrum Consistency Check

This utility was released in order to address a problem with the work remaining calculation in the version 1 process template.

Some customers have reported that the Work Remaining in a Product Backlog item in their Team Project is inconsistent with the total Work Remaining in the linked Sprint Backlog items.

It is possible in “normal operation” for this to happen. The following are the most likely causes of this behaviour:

1. Where a SBI is unlinked from a PBI and the SBI still had work remaining prior to being unlinked. Please reduce the Work Remaining to 0 and save prior to unlinking.
2. Where load conditions on the server cause the “eventing service” to timeout, the work remaining in this case would not be updated.
3. Where a PBI Work Remaining is edited from within Excel (unfortunately using the Excel add-in for TFS has the potential to overwrite a “read only” field).

Based on the above scenarios, the potential exists for the product burndown chart to show incorrect data. If the Work Remaining in a PBI does not burndown to 0 hours, the report will not show the item as being completed.

We have produced a tool “Scrum Consistency Check” in order to identify and resynchronise the Work Remaining on any project you believe to be “out of sync”.