Re: Necessity of Doc Plans for a Single Chapter or Section

[SteveFJong -at- aol -dot- com]

I don't think we are discussing the same scenario.

The scenario I have in mind, which I believe the original posting concerned, 
was a document where only one chapter is being revised. I think a doc plan is 
necessary, and certainly advisable, for all projects, even a minor update of 
an existing document.

To address the scenario I think Andrew has in mind, what if you're already 
working on a project and something changes? I think depending on the scope of 
the change, you can just do it under the original plan, but you should amend 
the doc plan if the change is substantial enough. Call it CYA if you want: I 
prefer to think of it as tracking changes and understanding why schedules or 
resource allocation might have to change. (I swear, sometimes dealing with 
project managers can be like playing backgammon: every time I turn around 
they want to double the amount of work 8^(

          -- Steve

Steven Jong--"Typo? What tpyo?"
mailto:SteveFJong -at- AOL -dot- com -dot- nospam
Home sweet home page: http://hometown.aol.com/SteveFJong

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Collect Royalties, Not Rejection Letters! Tell us your rejection story when you 
submit your manuscript to iUniverse Nov. 6 -Dec. 15 and get five free copies of 
your book. What are you waiting for? http://www.iuniverse.com/media/techwr

  Your monthly sponsorship message here reaches more than
  5000 technical writers, providing 2,500,000+ monthly impressions.
  Contact Eric (ejray -at- raycomm -dot- com) for details and availability.

---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit 
http://www.raycomm.com/techwhirl/ for more resources and info.