Re: How would you approach this?
Date: Tue, 4 Nov 2003 01:11:05 +0000
Message-ID: <k+WamtIpyvp$Ew7J_at_thewolery.demon.co.uk>
In article <64ea97cf.0310261908.51048256_at_posting.google.com>, Bruce
<brennie_at_dcsi.net.au> writes
>> > > > There are other requirements - but they are not known/defined at this
>> > > > stage. We were lucky to get this much detail. The CEO for the company
>> > > > we're writing this application for is a very hard man to pin down. He
>> > > > wants it now but he doesn't know what it is exactly. We had a five
>> > > > minute chat with him and, based on that, we come up with:-
>> > > >
>
>If the requirements are known to exist but are not yet defined then
>this also means that you do not have any way of knowing the required
>business rules for the client. Not only doesn't he want you to know
>his requirements, he also wants you to fail - for his personal
>aggenda. If you don't know what his aggenda is then it is foolish to
>even work with him - he is not being honourable in his dealings with
>you as the developer and it is then probable that he is not being
>honourable with anyione else either.
Don't you think YOU are being rather naive? When did you last have a client who knew what they wanted. Or, quite likely, even knew how to start trying to explain what they wanted!
Actually, you proved exactly that a bit further down, where you sat down and persuaded a client to go through and specify their requirements. The problem is, what do you do if they don't know how to explain that?
-- Anthony W. Youngman - wol at thewolery dot demon dot co dot uk Witches are curious by definition and inquisitive by nature. She moved in. "Let me through. I'm a nosey person.", she said, employing both elbows. Maskerade : (c) 1995 Terry PratchettReceived on Tue Nov 04 2003 - 02:11:05 CET