RE: What do you want/need to start a project

["Cliver, Barry" <CliverBarry -at- PRAIntl -dot- com>]

>>I am writing a little tip for engineers and analyticals on what they
should gather together to give the technical communicator to start a
project.

Ask for functional design docs, specifications, business case studies,
anything that helps you understand the product and the users. Ask if the
design docs get updated once they meet the real world. Good project
managers will.

Ask for access to a test environment so you can get "hands on" with the
project. Better yet, build your own environment that you can control.

Ask for dates: code complete, schema freeze, system test, integration
test, test drives, pilots, LA, GA, whatever your company uses. These
dates become your dates in writing/reviewing/delivering doc.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

WEBWORKS FINALDRAFT - EDIT AND REVIEW, REDEFINED
Accelerate the document lifecycle with full online discussions and unique feedback-management capabilities. Unlimited, efficient reviews for Word
and FrameMaker authors. Live, online demo:
http://www.webworks.com/techwr-l

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