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.
Re: Help on Coordination between Engineers and Technical Witers
Subject:Re: Help on Coordination between Engineers and Technical Witers From:David Neeley <dbneeley -at- oddpost -dot- com> To:Iliana Kostova <i_kostadinova -at- prosyst -dot- bg>, TECHWR-L <techwr-l -at- lists -dot- raycomm -dot- com> Date:Thu, 26 Feb 2004 14:15:15 -0800 (PST)
Iliana,
Greetings to Bulgaria!
Generally, I think the best practice is for the tech writers to attend principal design meetings at which progress is discussed. Originally, it is often helpful as well if the tech writers actually draft the software requirements document.
As a project progresses, the technical writing lead for the project should coordinate with the project manager to be sure that these problems are seen and resolved quickly on both sides. In addition, if you have quality engineers doing the testing, there should be close cooperation between the tech writers and the testers--for often, bugs are discovered by the tech writers as they work with the software as it is developed.
Whoever is in charge of quality or testing should already be tracking problems and changes.
