Thanks for all the ideas so for! Reacting to a couple of points.
==>*planning* to work overtime (especially for an extended period of
time) is not a good
Yes, I was aware of this when I made my original post.
==>PLANNING to work over for an extended time period will render your
developers exhausted and brain dead.
An extension of your previous post and one that I agree with.
However, this exact point was the reason for my post. I had *just*
finished a disucssion with a senior developer that told me, "When you
get 2x hours from me, you get *more* than 2x productivity from me."
This is a guy with 12 years experience that had come in a 5:00am,
because he was "in a groove". He challenged my assumptions on this
==>IMO, if the team voluntarily commits to goals
This is the crux of the problem. The team is excited by the goal &
might do so "voluntarily". If they have hesitation, its that they
know their spouse are not excited by the notion.
For example, my most senior developer says, "I'd rather be in here
writing code than fixing my leaky toilet at home. But, if I'm not
home to fix the toilet, the my wife has to pay somebody to fix it.
That's only acceptable to her, if I get some extra $$ to pay the
As his mgr, I'd like to find a way to have him excited & writing code
w/out the worry of the leaky toilet ;-)
--- In email@example.com
, "Victor Szalvay"
> I believe there is a general agile principle that *planning* to work
> overtime (especially for an extended period of time) is not a good
> idea (Kent Beck's book comes to mind). Scrum says that Sprint goal
> commitments are a bilateral agreement between the team and the PO.
> Here you have a team saying they can't meet certain goals and the PO
> is pushing back saying, "work overtime and we'll pay you more". I
> would caution that this could lead to a vicious cycle, especially if
> the team meets the goal by working overtime in the current
> PLANNING to work over for an extended time period will render your
> developers exhausted and brain dead. Ultimately they will become
> apathetic toward the project generally.
> IMO, if the team voluntarily commits to goals (and has
> underestimated), then working a little overtime to meet those
> committed goals is OK.
> -- Victor Szalvay
> Danube Technologies, Inc.
> --- In firstname.lastname@example.org, "magooski_79"
> <Mike.McGowan@l...> wrote:
> > Taking the "tacit knowledge" concept to a separate thread, I have
> > brainstroming question about incentive "pay" as it pertains to
> > methods.
> > I've got an Agile project currently running. Upper management
> > front line development mgr) wants to set some agressive new goals
> > deadlines for the project. General gut feel among the developers
> > this will take a significant additional time commitment. As a
> > result of the tacit knowledge already built up (and the tight
> > timeframes) it is also generally agreed that throwing additional
> > bodies at the problem is off the table. Quite naturally they
> > asking, "What's in it for me". I'm looking for any/all ideas
> > have been tried to address this & what your experience has been.
> > Ideas thrown out here so far:
> > * Pay market rate contract $$/hour for "overtime".
> > * Stock Options.
> > * A Sales-type "boondoggle"
> > * Additional professional conferences.
> > All ideas welcome.
> > Mike