The only thing to add to the discussion is in addition to a template
based, flexible framework and some input from a "designer" is using
agile techniques to keep the customer or end user in the loop
regularly. I can't tell you how many functional, good looking
applications I have dealt with that don't do what they are required to
do because the customer/end user wasn't involved in the design/redesign
cycle. Functional, good looking applications are worthless if they
aren't productive and do what the customer/end user needs them to do.
If you aren't regularly involving the target user, you may end up with a
great looking, functional, waste of money. Generally we fall into this
trap because we *know* what the customer wants (being the humble sorts
that we are).

IMHO,

Pete Helgren

GOOD WORDS!

How many times has a programmer just done what he or she 'thought or
assumed' the user wanted.
All it would have took was to pick up the phone or send an email to ask.

I just wonder how communication works with off shore projects?
I know that even in small companies, programmers do not communicate with
each other or the customer that well.
How could it be done with a language and distance barrier added on?
Or is it just so cheap and fast that it can be re-written 3 times?

Tom Deskevich





As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.