Re: [scrumdevelopment] Re: Impediment Reporting
- On Friday, October 1, 2004, at 3:18:39 PM, woynam wrote:
> The team has committed to delivering the features, provided that thereI could be wrong, but I had the impression that the feature set is always
> 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.
an estimate and that it is the sprint goal that is sacrosanct. I did NOT
have the impression that massive overtime was part of the Scrum process.
But I'm not a Certified Scrummaster, so I could definitely be wrong.
The central "e" in "Jeffries" is silent ... and invisible.
- Ken's CSM course does cover Scrum pre-project steps - at different
levels of detail for different situations: New Unfunded Projects, New
Funded Projects, Ongoing Projects, Fixed Price/Fixed Date Projects. In
my copy of the methodology book, these are grouped under the title
"planning" which occurs before the first Sprint Planning meeting.
> On Thu, 07 Oct 2004 12:22:32 -0700, todd <todd@p...> wrote:lack
> > The lack of a pre-project phase in all the methodologies is major
> > in my mind.
> I would not say this is true of Jim Highsmith's APM. Do others agree
> or have a different view?
> This could be an interesting discussion thread in its own right. What
> do you do wtih the work before a project starts or is funded?
> Alistair Cockburn
> President, Humans and Technology
> Phone: 801.582-3162
> 1814 E. Fort Douglas Circle, Salt Lake City, UT 84103
> _mailto_ (http://mailto/) : acockburn@a...
> _http://alistair.cockburn.us/_ (http://alistair.cockburn.us/)
> Author of
> "Surviving Object-Oriented Projects" (1998)
> "Writing Effective Use Cases" (Jolt Productivity Award 2001)
> "Agile Software Development" (Jolt Productivity Award 2002)
> "La perfection est atteinte non quand il ne reste rien a ajouter,
> mais quand il ne reste rien a enlever." (Saint-Exupery)