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: Engineering specs: The way it spozed to be? From:John Posada <jposada01 -at- yahoo -dot- com> To:stevefjong -at- comcast -dot- net, techwr-l -at- lists -dot- techwr-l -dot- com Date:Thu, 21 Sep 2006 11:47:39 -0700 (PDT)
> Paraphrasing the VP's concern: "I don't expect you to update the
> end-user documentation every time the engineers make a change. But
> I don't want them to update a spec every time they make a change,
> either. What is the triggering mechanism? What changes should be
> written down, and when? I want you to answer that question."
Around here, before a change can be made to a spec, the change is
submitted to the project and product managers. If they both agfree it
has validity, they then add it to the agenda of a regularly scheduled
meeting that includes all product stakehoders, including
representative from upper management, finance, customer suport, qa,
custom engineering, documentation, enginnering, change mnagement,
etc. At this meeting, the person(s) advocating the change to the spec
presents their case and it is discussed by all. At the conclusion of
the meeting, approval is either given, deferred, or rejected.
This meeting is taken very seriously because they know that a change
can have major impact on schedule and/or cost.
John Posada
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
Easily create HTML or Microsoft Word content and convert to any popular Help file format or printed documentation. Learn more at http://www.DocToHelp.com/TechwrlList
---
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-
