My response to the subject line - the differing team members should
discuss between them their differing estimate and arrive at an
agreed-upon number for the story. One of the team members may be
seeing complications that the other does not.
Then again, it could be as simple as the problem-space owner's
estimate verses the estimate of a switch-hitter programmer who is
not as up to speed on that specific problem space. The owner should
keep in mind that if the team goes with his/her estimate that he/she
will wind up having to do it because noone else will want to touch
it with that estimate on it. If he's fine with that, then the switch-
hitter can go help out someone else - otherwise compromise is in
order.
My point is that a single number estimate should be arrived at that
the TEAM feels it can live with - so that if something should
unexpectedly come up (like the problem-space owner having a baby
early or something) the rest of the team has a chance of taking over
the owner's stories and completing them close to the estimates. You
still have the inherent deficit from losing a person for the rest of
the iteration, but you don't also incurr a deeper deficit by having
pretended that you absolutely know who is going to implement what.
Dolores Scott
To Post a message, send it to: [EMAIL PROTECTED]
To Unsubscribe, send a blank message to: [EMAIL PROTECTED]
ad-free courtesy of objectmentor.com
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/extremeprogramming/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
