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.
"How do you make sure that the process for submitting, reviewing, and
approving a meeting with an SME will take less time than the meeting
itself?
"Wouldn't it be better to initially allocate a percentage of project
costs for unplanned meetings?"
I see that my original statement was not clear. I meant for the poster
to request addition of a single "Update Documents" activity that would
cover the time for *all* SME meetings. So the "submitting, reviewing,
and approving" would be a one-time affair, not once per meeting.
Any project manager has to, as Dan surmises, include some contingency
time in a project. But the less you have to, the better your results.
And it's easy to come up with an average amount of meeting time
required. I might be wildly off with one verbose and confusing SME, but
I've found that is always balanced out by some SME who, for example,
actually comments in her code as she goes.
Regards,
Jim
> -----Original Message-----
> From: Jim Morgan
> Sent: Wednesday, July 11, 2007 5:16 PM
> To: techwr-l -at- lists -dot- techwr-l -dot- com
> Subject: Re: Document Creation/Change
>
> ... The PMI Body of Knowledge calls for requiring
> prior approval for changes to virtually any part
> of the project plans or processes (called
> "Integrated Change Control"). *Unplanned*
> meetings with SMEs would fall under this...
>
> My recommendation is that you (James) find out
> how to submit a change request per the project
> management plan. Then submit a change that calls
> for addition of an activity called something like
> "Update Documents"...
>
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-