My general philosophy is to start at the end. Get with the users and ask
them what they want to end up with...the big picture. Let them brainstorm
for a while and write everything down. You can even ignite the brainstorming
session by offering ideas. Offer some super futuristic ideas (Example: You
withdrawal money from an ATM in Wisconsin and the Web application turns of
the lights in Steve's house in Charlottesville, Virginia.) because even if
they don't use your ideas you will spur them on to thinking outside of the
immediate need. It elevates your expert status when you offer suggestions on
how to use the Web in wonderfully new ways!
Then move back toward the specific parts of the site, asking many questions
about how it will be used, why it is being developed, etc.
Once each section of the site is brainstormed, start organizing the
information into the circuits and fuses that so many others have already
discussed.
Then lock yourself in a room and code for 5 days. :-)
Actually the 5-day code-a-thon works well if the specs don't shift. I am in
Day 3 of my 5 days on a new project. It is very cool to sit down and just
write code...the challenge I am having is the client is calling and asking
about adding or changing functionality AFTER the specification has been
written. I guess that is one definition of Heaven...all of the projects you
want with no clients or users to "get in the way". :-)
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
