I'm ++ this and it's thread. It's a good point.

As a developer it is your responsibility to make a good faith estimate and stick to it.
At first I read this and though "woah" but your explaination afterwords made it "ok".

I think, when it comes to developing web-related products, that a sign-off on specs is often quite hard to get. Sure, you can mock up sample report-pages (fyi: I write applications that are based on IE->Apache->mod_perl->Sybase.. so, "web related") and go from there, but that's never quite "enough". This column header needs changing, the math behind calculating that value is "right" but for this specific case, it's wrong..

I think spec signoff is do-able as long as the business rules in place are static.

We get a lot of the users with the "the report shows the wrong data, it's a report problem" mentality, when in fact, it's a spec change for a specific "rule" that was forgotten..

But, you are right. As long as you think CMA then you should have enough information to present to your boss(es) when they ask where/what/how long a project will be before it's done..

One4k4 - perlmonks@poorheart.com (www.poorheart.com)

In reply to Re: Re: The IT Project Estimation Game by one4k4
in thread The IT Project Estimation Game by grantm

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.