from the step-one-invent-time-travel dept.
itwbennett writes "It can take a fairly stable team of programmers as long as six months to get to a point where they're estimating programming time fairly close to actuals, says Suvro Upadhyaya, a Senior Software Engineer at Oracle. Accurately estimating programming time is a process of defining limitations, he says. The programmers' experience, domain knowledge, and speed vs. quality all come into play, and it is highly dependent upon the culture of the team/organization. Upadhyaya uses Scrum to estimate programming time. How do you do it?"
"The Avis WIZARD decides if you get to drive a car. Your head won't touch the
pillow of a Sheraton unless their computer says it's okay."
-- Arthur Miller