So you're saying that the actual bare minimum when a door is ordered is that it functions as a door in an opening, fully installed. That's pretty understandable if the door is ordered by an end user tenant. If the property owner wants to hang the door, you don't have to hang the door. If it's a construction contractor who orders a door from you but hinges and latches elsewhere, they just want a door. If someone wants what's called a pre-hung door -- that is, one with hinges attached and an attached jamb that then is inserted into the rough frame -- then they get the hinges and jamb. If I order a slab door from you, paid someone else for the latch, paid someone else for the hinges, and paid another party to assemble and install the pieces I probably don't want you to send a workman and additional hardware. I just want the door.

"Give the customer what they ask for" is not shorthand for "screw the customer over by misrepresenting your agreement to get out of work". You should gather the requirements and deliver what's required. Just as you shouldn't short the customer by delivering much less, you shouldn't short yourselves by delivering a bunch extra. The customer would rather pay you no more than necessary, and any extra time you have to give them they'd rather get the extra features THEY want, not what you GUESS they MAY want. When you're coming in way under budget, make that extra customer meeting about whether they want early delivery, a partial rebate (horrors!), or WHICH extra features they may want included in the original price. It's much better, trust me, then the meeting THEY call to ask why you overpriced their initial requirements to provide all this fluff they didn't ask you to write.

In reply to Re^8: Beyond Agile: Subsidiarity as a Team and Software Design Principle by mr_mischief
in thread Beyond Agile: Subsidiarity as a Team and Software Design Principle by einhverfr

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.