True - they need to accept that you delivered what they said they wanted and if they now want something different, someone has to 'pay' for the effort to implement it. But, in my experience, it is important to set the expectation at the outset that this is what will happen, so the initial estimate includes a proof of concept or pilot and a couple of iterations.

People almost never know what they want until they have something that they can play with. Then they are able to say "yes, this is what I want except ...".

The problem with documenting a spec before starting work is that it is very hard to strike a balance between the document being precise enough to be useful (and uncontestable after the fact) and the document being accessible enough that it will actually be read and understood. If I write a spec that someone misinterprets and signs off in error, then I should share the blame.

I do agree the importance of documenting things up front. However the point of documenting is so that everyone's expectations are in sync and (IMHO) one important expectation that everyone should have is that developing a solution is an iterative process.

In reply to Re: Re: Re: Re: What do they want? by grantm
in thread What do they want? by schumi

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.