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: Documentation and Master Plan From:"Mike O." <obie1121 -at- yahoo -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Thu, 17 Feb 2005 10:24:35 -0800 (PST)
Joe Campo wrote:
> John Posada wrote:
> > Frankly, I'd much rather write it myself than spend a month
> > trying to convince a bunch of PHBs of the value of
> > documentation (yes, I have done it both ways).
Actually that was my quote, not John's.
> Also, it does no good if only you and the highest level
> know about it. It HAS to be integrated into the entire plan.
That's why I suggested asking the PM to merge your updates with the
master plan. It's just easier to give him the task list than to argue
for permission. YMMV; I'm just describing what has worked for me.
> How do you expect product engineering to know where there their
> impacts are for say, building in MapIDs for context help.
Because your doc plan will include milestones titled something like
"Receive MapIDs from dev team" and will name the specific resources who
are on the hook to deliver them to you, and your PM software will
identify this milestone as a required predecessor task to completing
the online help deliverable.
> How can QA include the time to verify that help works as designed?
That's the QA manager's problem. Just *you* make sure it works.
> ow do you know at what stages deliverable are due? They doesn't
appear by magic. ?
Communication, teamwork, and experience. Or you could just ask. For the
doc deliverables *you* are the one specifying at what stage all the
interim deliverables will be done (timeboxed by the overall schedule,
of course).
Mike O.
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
WEBWORKS FINALDRAFT - EDIT AND REVIEW, REDEFINED
Accelerate the document lifecycle with full online discussions and unique feedback-management capabilities. Unlimited, efficient reviews for Word
and FrameMaker authors. Live, online demo: http://www.webworks.com/techwr-l
Doc-To-Help 7.5 Professional: New version with new features, improved performance and reliability, plus much more! Download your free trial today at www.componentone.com/techwrlfeb.
---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit http://www.techwr-l.com/techwhirl/ for more resources and info.
