Take the 2-minute tour ×  Iteration has already started, new
programmer joins the team, task X has already been estimated to
be 30 hours by a different developer.  What is the best practice
in this situation?    • new developer runs with the given
estimate (the idea being that any discrepancy will be corrected
for when velocity is calculated?)   • new developer re-estimates
task? (if so, what if it's significantly higher and no longer
fits in the iteration?)   • throw our hands up and go back to
waterfall?   • something else entirely? share|improve this
question  3 Answers 3  up vote 5 down vote accepted  What I say
is:  New developer re-estimates the task. If it has to be moved
out of the iteration then it gets moved out.  You don't know if
the new developer is going to be able or not to do it in the
time the original developer though it will take. And with agile
methodologies is the developer that does the work the one that
should say how long it will take.  Furthermore, I would apply a
multiplier (how big