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.
Subject:Re: multiple TWs for a project From:"Anthony Markatos" <tonymar -at- hotmail -dot- com> To:gyaker -at- csc -dot- com, techwr-l -at- lists -dot- raycomm -dot- com Date:Wed, 09 Feb 2000 14:34:49 PST
Gil Yaker asks:
What's it like working on a team of tech writers? Lets say 1, A small team
of 3-5 and 2, a larger team like the type that would work on a highly
Tony Markatos responds:
It depends on how well the project is managed (planned). If the project was
properly partitioned - "chunked" in TW terminology, then things will go
pretty smoothly. (Note: the chunks become the work breakdown structure.)
In properly chunked projects, all procedure to accomplish a given task will
be together. (The end-user will not have to jump around between different
sections of the documentation to accomplish the task.)
In writing a properly chunked document, the TWs will not have to do a lot of
coordinating between themselves. It is in coordinating the different chunks
that major disagreements occur.