Down time

[Leigh Price <price_leigh -at- yahoo -dot- com>]

I have a question for the folks who write software
documentation. How much down time do you typically
have between projects? The company that I currently
work for releases a major version about once a year,
with a couple of "point" releases in between. I am
finding that the time in between finishing one release
and starting the next is growing, with the result that
projects end up feeling like death marches. For
instance, we finished a point release in mid-July
and have been are still waiting for rollouts to begin
for the next release. Is two months of down time
unusual?
 
In many ways, this amount of time between projects is
nice--we have accomplished a lot of things that would
otherwise fall off of the radar. In other ways, it
isn't so great. I try not to dwell on the fact that,
two years ago, I was half done with my writing
assignments for a product released in the first
quarter of the following year -- the same timeline for
the project I am waiting to start working on.
 
Thanks,
 
Leigh


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

ROBOHELP X5: Featuring Word 2003 support, Content Management, Multi-Author
support, PDF and XML support and much more!
TRY IT TODAY at http://www.macromedia.com/go/techwrl

WEBWORKS FINALDRAFT: New! Document review system for Word and FrameMaker
authors. Automatic browser-based drafts with unlimited reviewers. Full
online discussions -- no Web server needed! http://www.webworks.com/techwr-l 

---
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.