RE: Process Documentation

["Wilcox, Rose (ZB5646)" <Rose -dot- Wilcox -at- pinnaclewest -dot- com>]

>Hi Wrlers,
>By next Tuesday, I have to come up with some ideas for documenting a work 
>process. [snip]


I will also add one more note.  A process can span several groups or roles.  Make sure the roles are defined in the document, along with responsibilities.   You might consider a tabular form.  Many of my clients love a step table showing the task and who is responsible for it, something like:

1.  Enter the bug fix request in the Super Wonderful Bug Tracking system.    Anyone
2.  Assign the bug fix a priority code.                                      QA Manager
3.  Assign the bug fix to a developer.                                       Development Manager

etc....

Also many of my clients have found process flow charts helpful.  

Rose A. Wilcox
Projects and Deployment
Communications Specialist / Technical Writer
Rose -dot- Wilcox -at- PinnacleWest -dot- com
602-250-1564
"I can write better than anybody who can write faster, and I can write faster than anybody who can write better." 
	- A. J. Liebling (1904-1963) 






^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Absolutely FREE! FrameMaker/Win 6 & 7 Express Customization (v3):
Quick-access buttons & keys to common functions, char tag/font drop-down
lists, charset browser, QRef guides & much more: http://www.microtype.com/2

Check out the new release of RoboDemo, our easy-to-use tutorial software.
Plus, buy RoboHelp Office in August and save $100 with our mail-in rebate.
Get details and download free trial versions at http://www.ehelp.com/techwr-l

---
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.