I've found many, maybe most, customers don't have a good idea of what they actually need (I only do web-work professionally; back and front end). There is a dialog and chance to apply expertise there, not guessing, or the price-padding fluff you somewhat unkindly allege. Bare minimum, while I understood you were speaking in code for some kind of ship early best practice, would be interpreted as cheap, half-baked, or rip off in most industries. Were the cleaners good? They did the bare minimum. How's the new car? It's the bare minimum.
"I need a customer contact form," is a typical requirement for a website. Bare minimum could be interpreted a few different ways there and different levels of expertise will apply different standards. That's about as simple as the stuff gets and it's still ambiguous.
Again, I did say I knew you knew this stuff. Throwing out things like "trust me..."? And CAPS? No, you TRUST me! :P
In reply to Re^9: Beyond Agile: Subsidiarity as a Team and Software Design Principle
by Your Mother
in thread Beyond Agile: Subsidiarity as a Team and Software Design Principle
by einhverfr
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |