Re: SDLC Documentation
Also make sure, in whatever sneaky way is appropriate, that you are not being made a scapegoat for a failed project. "We couldn't get it done on time because the tech writer was too slow. And he kept finding bugs in it." (Even though we only gave it to him a week ago.)
--
This email has been checked for viruses by Avast antivirus software.
www.avast.com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | https://techwhirl.com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com
Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.
Looking for articles on Technical Communications? Head over to our online magazine at http://techwhirl.com
Looking for the archived Techwr-l email discussions? Search our public email archives @ http://techwr-l.com/archives
References:
SDLC Documentation: From: Jason L
Re: SDLC Documentation: From: Gene Kim-Eng
Re: SDLC Documentation: From: Peter Neilson
Previous by Author:
Re: SDLC Documentation
Next by Author:
SDLC Documentation
Previous by Thread:
Re: SDLC Documentation
Next by Thread:
Re: SDLC Documentation
Search our Technical Writing Archives & Magazine
Visit TechWhirl's Other Sites
Sponsored Ads