Hello,
I imagine that many of you develop Perl with real world constraints--
deadlines and budgets. Whether you deliver your work internally or to an
external client, a good estimate plays an important role in the ultimate
quality of the software.
You may well have experienced working on a project that was estimated
too low: stress rises, as does the temptation to priority delivery time
over quality.
So, what resources are recommended to consult to make great estimates?
What habits to develop?
I know that before the good estimate comes the strong technical
specification so you can know what you are estimating-- that much I think I
do well at. I have also read about the 'XP' model, but I find it does
map well onto smaller "one off" projects that flow through here.
I also wouldn't mind hearing stories about "software estimates in the
real world", the good the bad and ugly.
Thanks!
Mark
--
. . . . . . . . . . . . . . . . . . . . . . . . . . .
Mark Stosberg Principal Developer
[EMAIL PROTECTED] Summersault, LLC
765-939-9301 ext 202 database driven websites
. . . . . http://www.summersault.com/ . . . . . . . .
