Ben Rubinstein wrote:
Keeping these users motivated, by taking the time to record that the bug has
at least been read; certainly by recording that it has been put on the
internal tracking tool ("assigned?"); and by making part of the engineer's job
when they change the status in the internal tool, to also update the external
one, is far far cheaper than any other possible way of getting that level of
testing done.
Well said, Ben.
Because my expectations for the RQCC are different from others, it has
been easy for me to overlook the role it could potentially play in
keeping participants motivated.
Your note was a good reminder along those lines. Thanks.
--
Richard Gaskin
Fourth World
Rev training and consulting: http://www.fourthworld.com
Webzine for Rev developers: http://www.revjournal.com
revJournal blog: http://revjournal.com/blog.irv
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
