Re: What do you say....

[rob_lamora -at- infinium -dot- com]

Well, like it or not, software development revolves around the developer.
But, you should not let this go without fixing as much as you can fix,
such as:

* Marking review hard copies with a date or revision number so that
reviewers know if they are current.

* Ensuring that reviewers have the latest review copy... one way to do
this is to have a Review cover sheet that provides a checklist for the
reviewer. One of the steps for the reviewer is to verify the version of
the document under review. If you have a company Intranet, consider
placing the most up-to-date review copy there, so that it can be acccessed
by anyone.

* Communicating and strictly enforcing review timeframes. Follow-up
communication during the review cycle to confirm review end dates is
important. Send out a "thank you" email to all reviewers following the
review cycle.

If these checks and balances are in effect, then you should tell the
developer that his/her edits missed the review period but will be
considered with the next release. If it continues on subsequent releases,
find yourself another reviewer.

Just my two-cents, for what it's worth.


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Order RoboHelp X3 in November and receive $100 mail in rebate, FREE WebHelp
Merge Module and the new RoboPDF - add powerful PDF output functionality
to RoboHelp X3. Order online today at http://www.ehelp.com/techwr-l

Check out SnagIt - The Screen Capture Standard!
Download a free 30-day trial from http://www.techsmith.com/rdr/txt/twr
Find out what all the other tech writers, including Dan, already know!

---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit
http://www.raycomm.com/techwhirl/ for more resources and info.