These points assume that the clients know what they 
want ahead of time.

[download]
I see where you are going but if you don't know what you want why do you want me to do something that you will change? 
Making people sign off on requirements ahead of time 
isn't a great idea

[download]
I have to disagree here. If this was the case then there would be no need for a business case for a project. A business case has a set of goals and requirements with indicators as to how those can be met (so measured against). Of course the requirements may change but then they can only do so in the face of the business case. If the business case doesn't marry with the changed requirements then either must change. If the business case changes then it needs re-approval as the sponsor or steering group may need to understand the scope of this change. It may change how someone does their job, how long a process takes (etc).

It also means that the project timescale and timeline has changed.

Finally there is a difference between the following (using your example): 
all textures will be created from a bitmap.

[download]
and this 
All textures will be created by our designers. We must 
agree the formats the application will support as part
of the new workflow in the design team.

[download]

In reply to Re^2: OT: Project clients by simon.proctor
in thread OT: Project clients by simon.proctor

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.