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.
Yes, the meeting part of the scheme is the goofy bit, as I mentioned
in my original post on the subject. Normally, the only thing controlled
by the product owner would be content and how and when the
decisions to initiate and release content change takes place, not how
possible change is discussed before it is offically proposed.
What Jim described could be an office power struggle. Or it could
be that the PMO is the only one willing to step up to the plate and
take ownership of an out-of-control process. If this scheme is being
imposed across the board on the product development process, i.e.,
engineering has to get the same approvals to make changes in design,
it's possible that the main target of it may be the engineers who are
requesting the doc changes and not tech pubs at all.
Gene Kim-Eng
----- Original Message -----
From: "Mary Arrotti" <mary_arrotti -at- yahoo -dot- com>
To: "'Techwr-L List'" <techwr-l -at- lists -dot- techwr-l -dot- com>
Sent: Tuesday, July 10, 2007 11:58 AM
Subject: Re: Document Creation/Change
> There is nothing inherently advanced about moving to a system where one group (PMO) controls when, how, and why another group
> (doc) meets with a third group (dev). This is what Jim described and what I primarily responded to.
> Companies have power struggles. And from what Jim wrote, it sounds like that's what he's dealing with now.
> I agree that it's important for product management to be involved in deciding what documentation is provided and be part of the
> review and approval process. My company feels this so strongly that doc is within the PMO hierarchy.
> What's different & unusual is for PMO (if a separate group) to control the doc process - how the documentation group works and
> interacts with other groups. Since this is a proposed process change, I do think it may be useful for Jim to find out how his
> management wants to handle this & how it would impact his/his group's effectiveness.
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-
