The team has committed to delivering the features, provided that there
are no major impediments that aren't cleared in a reasonable amount of
time. If the impediments are identified, and they are not removed, the
team should not be held to the original feature set.
From another angle, features can be removed from a sprint with the
approval of the product owner provided that the team made a good faith
effort in upholding their end of the "contract". They should not be
forced to work extended hours through no fault of their own.
However, if the team violates one of the basic principles of Scrum,
openness and honesty, by withholding knowledge of major impediments,
then I see can see where they could be "penalized" by having to work
overtime to meet the sprint's goals.
Of course, in the perfect world this shouldn't happen. Unfortunately,
as some groups and individuals are exposed to Scrum, they may have a
hard time embracing the amount of openness necessary for Scrum to
work, or may be actively attempting to derail the process. :-(
--- In firstname.lastname@example.org
, Ron Jeffries <jeffries@d...>
> On Friday, October 1, 2004, at 7:47:06 AM, Pete Bevin wrote:
> > The speech I give these days is "If you as a team sign up to these
> > backlog items, it means that come hell or high water, you have to
> > deliver them by the end of the sprint. So if there is anything
> > stopping you from doing that, you have to let people know sooner
> > rather than later, otherwise there are going to be some very late
> > nights four weeks from now."
> The above does not feel to me to be in the spirit of Scrum and Agile
> methods. Am I missing something?
> Ron Jeffries
> Scientists discover the world that exists;
> engineers create the world that never was.
> -- Theodore von Karman