Paul, that's a great question, and one that is faced by every database
developer.
The core issue is about communication: how do you communicate with the
client to *hear* exactly all they want? How do you communiate to the client
what is included and not included in your spec/quote? The reality is that
this takes quite a bit of work.
It actually takes me 1 - 4 days to write this document that defines exactly
what the database will do, what data will be stored, what reports will be
generated, documentation, support, security, system requirements, etc, etc.
During that time, I have scripted out the data structure on paper, and buit
it in an mdb. Only then can I know for sure that what I have defined is
doable (there's no gaping holes, or unanticipated "manys"), so I know I can
fulfil what is promised and make a reasonsable estimate of the amount of
time involved in creating this database, and hence a fixed quote. The
document will be around 5000 - 10000 words in a fairly terse style. I do
charge for this "business analysis."
Although that's quite exacting, my experience is:
a) I waste less time with people who want something for nothing (so don't
want to do the analysis.)
b) This process goes a long way towards building trust with the client, who
needs to know that you are able to deliver what you promise.
c) This process helps the client think through what they really want, and
identify issues they did not think of.
d) It cuts out so much frustration and backtracking later in the project,
trying to fill in the missed areas.
e) If there are additional items the client wants later, there is no
argument about what was included and what is additional.
f) This document becomes the foundation for developing the project, i.e. you
work through all the items you specified, ticking them off, and you know
exactly whether you are on track and on time.
g) The documentation stage spells out more detail on each section, but
essentially covers the same items, so as you test and write your
documentation you are cross-referencing the original promise.
i) The original, clearly defined and comprehensive spec lays a great
foundation for on-going, clear communication with your client, that
continues through the project, deployment, and into the support phase.
j) You have empowered your client to be clear and precise in their
communications with whomever else they have to explain this project to
(board of directors, manager, finance dept, ...)
Again, this is quite a bit of work to do it this way, but the clear, open,
detailed communication is the key to lasting satisfaction and good client
relations. I'm not kidding about the work, but IMHO it's really worth the
effort.
HTH.
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users -
http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"Paul H" <no****@nospam.com> wrote in message
news:le*****************@newsfe4-gui.ntli.net...
How do you folks get a reliable and complete brief of what is required
before development starts?
I am forever going back to a client once a project has started saying
"Hang on, now that I've started building this I realise what you want is
impossible, we'll have to do this way instead....etc.."
OK, so this is partly down to me not getting all the facts from day one,
but if the client does not give detailed, accurate instructions there is
not a lot I can do. I feel that most clients think they can show me a
report or a spreadsheet and say "Make a database out of this." and I'll
wave a magic wand and deliver.
The normal scenario for me is:
1. Meet with client to discuss requirements, I take notes and copies any
relevant data.
2. I type up what *I* believe the brief is and fax that to the client with
the quoted price.
3. I start work and find there is loads more to do than I thought
So how do I avoid this constant toing and froing during development and
get a client to write a coherent brief from the start?
Thanks.
Paul