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: Number of Projects From:G J Lundy <glundy -at- INFOCOM -dot- NET> Date:Thu, 21 Sep 1995 21:54:08 GMT
Part of the difficulty of these side-by-side projects is that available
resources (e.g., other
technical writer and editor) are being assigned to projects that do not allow
them to be used as
supplemental help. The company will not hire contractors, and none of the
management level
people are intimately familiar with the problems of developing and writing
documentation. The
other problem relates to the fact that we have over the past year moved into a
product-driven
scheduling, but many of the finer points... such as technical documentation, are
still not included
along with project teams, or information listings. All of which adds
considerable burdens to
obtaining information, resources and staying in-the-know with whats going on.
The schedules
are be set by upper management, but without the benefit of input or modification
from those that
have to do complete the project(s). When slippage occurs.... it's a really big
deal!
