Sometimes you have to fire the client. I know, easier said than done when there are bills to pay, but I've had luck calling the bluff. The right client shapes up and you move forward in a productive way for all concerned. The wrong one would have been a money/time/reputation killer anyway so you move on quickly in to the next "right" one. It's a hard to quantify opportunity cost thing.
Sent from my iPad
On Feb 21, 2013, at 7:42 PM, Andy <[address removed]> wrote:
Right. Agile doesn't mean no requirements, nor does it mean give me every requirement, fully and finally detailed, up front. Agile is simply a responsive, iterative process wherein one applies "just-in-time" paradigms to things such as analysis and documentation. Can't live without a doc in the end, otherwise how do multiple teams work together? How do multiple organizations work together? How does a builder get paid by a client and avoid litigation? Requirements documentation, that's how.
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by Andy ([address removed]) from NY Tech Meetup.
To learn more about Andy, visit his/her member profile
Set my mailing list to email me As they are sent | In one daily email | Don't send me mailing list messages
Meetup, POB 4668 #37895 NY NY USA 10163 | [address removed]