Re: [scrumdevelopment] Incentive Pay - was Re: Part-timers
In my experience what is in it for them is a job - just a little sarcasm. Anyway, paying for overtime usually doesn't work - in my experience there is little correlation between those who work overtime and those who get the job done. I would pay a bonus if the project meets it's deadlines.
Taking the "tacit knowledge" concept to a separate thread, I have a
brainstroming question about incentive "pay" as it pertains to Agile
I've got an Agile project currently running. Upper management (I'm a
front line development mgr) wants to set some agressive new goals &
deadlines for the project. General gut feel among the developers is
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 are
asking, "What's in it for me". I'm looking for any/all ideas that
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.
--- In firstname.lastname@example.org, "Alex Jouravlev"
> Agile methods are based around reliance on tacit knowledge. There
> truly unique people on our industry, however as a general rule a
> part-timer's ability to operate on tacit knowledge is much less
> Alex Jouravlev, Principal Consultant
> Business Abstraction Pty Ltd
> phone: +61(0)4-0408-3248
> -----Original Message-----
> From: J. B. Rainsberger [mailto:jbrains@r...]
> Sent: Monday, 31 May 2004 5:35 AM
> To: email@example.com
> Subject: [scrumdevelopment] Part-timers
> Kent J McDonald wrote:
> > Let's assume you were in a situation where it was the norm for
> to be
> > assigned "part time" to projects lets say because the skill base
> > specialized and certain people are needed for tasks, but not
enough for an
> > entire month. How would you suggest organizing the team to
> > case.
> > I ask that question knowing that theoretically, the environment
> set up
> > different where everyone on the team would pitch in and do a
> > everything and people could be assigned to only one project at a
> > however currently consult at a company that exists in an non-
> > but am trying to apply some of the practices/principles on my
> The problem here is a velocity problem: you can't accurately
> much you can accomplish in a given sprint. For that reason, I
> shorter sprints to counteract the volatility of the resources. When
> don't know how many people you'll have next week, there's not much
> planning beyond this week.
> J. B. Rainsberger,
> Diaspar Software Services
> http://www.diasparsoftware.com :: +1 416 791-8603
> Let's write software that people understand
> To Post a message, send it to: scrumdevelopment@e...
> To Unsubscribe, send a blank message to:
> Yahoo! Groups Links
To Post a message, send it to: scrumdevelopment@...
To Unsubscribe, send a blank message to: scrumdevelopment-unsubscribe@...
- Hi Bryan,
"Just as an FYI, I have posted an example of a sprint backlog using
MS Project to the Scrum Alliance website."
I was interested in your MS Project example, but can't find it. Can
you direct me to where it is, or send me a copy?