> hey want to revise the sprint
By this above statement, do you mean they want to drop a PBI from the Sprint?
(I had a little trouble following what you meant by Sprint Backlog Burndown and SBI burndown. Did you mean PBI instead of SBI? If so, does your PBI burn down in points or something?)
Charles Bradley, CSM, PSM I
Experienced Scrum Coach
My blog: http://scrumcrazy.wordpress.com/
From: Tara Santmire <tara@...>
Sent: Wed, May 4, 2011 9:39:40 AM
Subject: [scrumdevelopment] Sprint Burndown Team Morale Meeting Commitments Question
My team runs two burndowns during the sprint. A SBI burndown and a Sprint Backlog work remaining
burndown. For the Sprint Backlog burndown we estimate tasks for all SBIs in remaining work hours and update the remaining work hours at the Daily Scrum every morning. The team is very enamored of looking at the resulting graphs to see if we are on track both in terms of remaining work vs. remaining capacity and items completed.
Sometimes remaining capacity gets reduced by uncontrollable factors such as a team member is out sick for several days.
Sometimes unexpected events occur which add unanticipated work such as developer machines going belly up and having to be rebuilt before the developer can do work planned for the Sprint.
In either case the team is really getting wrapped around the axel about
not meeting the sprint commitment and they want to revise the sprint commitment so that the graphs come out nicely and commitments are “met”. Their reasoning is it’s not their “fault” that they can’t make the commitment and so the “records” should show that they made a reasonable commitment given the “unexpected events outside of their control”.
Thoughts about how to handle this?
Tara Santmire, CSM, PMP