 07-03-2007, 11:57 AM
|
Scrum for Team System
Joined on 03-26-2006
Posts 18
|
Announcement: Work Remaining consistency checker tool available to download.
|
|
|
|
|
We have been made aware of some customers who 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 an SBI is marked as deleted (v1.0, v1.1). This would not cause resynchronisation, and this can be resolved by installing Scrum for Team System 1.2.
3. Where load conditions on the server cause the “eventing service” to timeout, the work remaining in this case would not be updated.
4. 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”, and it may be downloaded from:
http://download-uk.scrumforteamsystem.com/dl/ScrumConsistencyCheck.zip
The utility has options to check and optionally resynchronise the Work Remaining for a specific Team Project. Please raise any queries about the utility on the forum: http://scrumforteamsystem.com/forum
Scrum for Team System Product Group
|
|
|
|
|
Report
|
|
|
|