On Feb 16, 2011, at 12:25 PM, Ricardo Aráoz wrote:
> In worst case scenarios you ask the user if the system is ok, and if he
> says yes, you tell him you'll drop by tomorrow noon for him to sign that
> he has tested the system and it is so far acceptable. You keep doing
> that every step of the way. It's my experience that when a user has to
> sign up something he'll rush to do the proper testing. And if that's not
> the case then responsibility is clearly outlined and you may even get to
> charge for xtra time.
It isn't the users' job to test - that's part of the development cycle.
It's the users' job to give feedback, and the more opportunity for
that, the better the quality. I've had users who noticed something they didn't
like while using the system, but by the next time they were asked for feedback,
they forgot about it. I've also had users tell me they thought something wasn't
working right, but didn't want to say anything so that they wouldn't look
stupid if it turned out that they misunderstood how to use the program.
Having frequent opportunities for feedback is important, but so are
frequent releases, so that users can see that their feedback has an effect.
When a user suggests something and less than a week later they see their
suggestion implemented, that goes a long way toward a successful project.
-- Ed Leafe
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
