Re: [scrumdevelopment] Impediment Reporting
- On Friday, October 1, 2004, at 11:36:32 PM, Marc Hamann wrote:
> So if you find that happening, I don't think it is unreasonable to let theThere are few notions expressed in the agile arena with which I disagree
> team suffer with unacceptable overtime, keeping the hope that they will
> self-organize into sustainability in reaction to this by developing the
> courage to speak up when changing conditions make the original promises
> impossible to sensibly deliver.
> The price of the freedom and joy that Agilists seek in their work is
> responsibility and discipline. And sometimes those values are painful
> before we master them. Letting the team both suffer and enjoy the natural
> consequences of their choices is part of the inherent power of Scrum (and
> like approaches), and I think it is almost the duty of the Scrum Master to
> let that happen, and point it out when it does.
more than the above.
Do only what is necessary. Keep only what you need.
- 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)