Re: [scrumdevelopment] Impediment Reporting
- Ron Jeffries wrote:
> On Saturday, October 2, 2004, at 12:21:55 AM, Dion Stewart wrote:What is overtime? 40 hr per week is a made up number. 50 hr per week is
> > Forcing people to work overtime doesn't change their behavior.
> Nor does it get more work done, or better work done. Quite the contrary in
> most cases.
acceptable amount of time. There's no reason for a drop in quality at 50
Personally, anything above that on a sustained basis, i can't do. And i know
that because i have the feedback of my tests and velocity.
If i am at startup, we have X funding, we have Y truly required
features, release date
Z, and T total person hours, then i can't be so religious about the
hours i work.
Yes, i know all the tradeoffs, but working more, as long as you are
is a necessary option. When you sign up to a startup you know what the
And you always know when quality is dropping so you can adjust accordingly.
I can't imagine an absolute rule based on no research being a good basis for
deciding how long to work.
- 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)