TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
All,
It is now time to solicit
feedback/comments/additions/deletions/recommendations from a team of
about 10 developers on a 1100 total page System Design Document that has
been broken down into 7 parts (each a separate WORD document). Document
is stored on SharePoint and all team members have access to it.
All prior documents have been much smaller and the reviews went
relatively smoothly....
I'm struggling a bit with determining the best method to obtain the
developers cooperation in the review process as I don't have a lot of
experience with this.
Is someone aware of guidelines or an overview article that addresses
what the tech writer should keep in mind in order to obtain the needed
review cooperation from developers most of whom appear have a near zero
interest in the documentation for their IT solution?
Thanks,
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today!. http://www.webworks.com/techwr-l