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.
> Don't get me wrong. A defined process doesn't have to be a 200 page
> manual with flowcharts, gantt charts, DFDs, and various UML stuff.
> It could be a one page document. In fact, it could be totaly in
> head. However, what's important is that you know what you are
> doing, what you will be doing next, at what percentage of the
> project each element should happen, and that you follow the same
> process each time.
HOWEVER...the larger the effort, the more formal you need to make
your process, possibly including UML, DFDs, FDs, SDs, TDs,
interdepartmental Gantts, etc.
- The larger the effort, the more other people have at stake and
they want to know that you know what you are going to do before you
do it, if only because they want to know where they stand in it. "I'm
gonna write like hell" doesn't do much for them.
- The larger the effort, the more interaction you have with other
groups. In some of my past efforts, some of what I wrote was then
taken by development and incorporated into the application. When they
can get this from you and by when you need to have it ready requires
- The larger the effort, the larger the pieces, and when a piece goes
to hell, the larger the impact. A small impact can usualy be fixed by
working late a couple of nights. A large impact can require $$$ and
the enlistment of outside resources and they aren't sitting around
waiting for your call.
Senior Technical Writer
"I think the problem, to be quite honest with you, is that you've never actually known what the question is."
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
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include single source authoring, team authoring,
Web-based technology, and PDF output. http://www.DocToHelp.com/TechwrlList
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-