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.
Well, we tend to do that. Our software is not "off the shelf" though, so we
can anticipate a couple of months after the release before a client
purchases the software and we have to install and configure it for them.
That gives me time to finish up the major updates, which is good because
there's only me.
In a perfect world (like my previous job) documentation efforts began at the
same time as develop efforts and the two would be ready to go to QA at
roughly the same time (give or take a week or two).
How acceptable it is to have a lag time I think depends on the situation. If
your software will be in stores with the documentation included, there
shouldn't be any lag time. If your documentation is delivered over the
internet (as more and more software vendors seem to be doing) a bit of a lag
time may be acceptable. The software needs to be published, packaged and
delivered to whatever retail outlets are appropriate. This gives the
documentation a bit of time to "catch" up.
Hmmm, maybe that's why software vendors are using online documentation more.
Suzette Leeming
Stouffville, Ontario
On 3/27/08, Sharp, Sandra <sandra -dot- sharp -at- cgi -dot- com> wrote:
>
> For previous releases, we've been able to provide documentation in time to
> be packaged with our software. However, due to the Tech Comm team's reduced
> capacity, we will not be able to do so for an upcoming release. I'm creating
> a plan that I think is reasonable for the amount of time the two of us will
> need to complete the documentation post software delivery. Wondering if it's
> not uncommon for shops to publish documentation after SW delivery? What is
> the expectation? How acceptable is it to have a lag time between software
> delivery and documentation delivery?
>
>
>
>
> --
> "What I like to drink most is wine that belongs to others." - Diogenes
>
> Please consider the environment before printing this e-mail
>
> Need affordable web hosting? I recommend 1 & 1 - that's where I'm hosted!
>http://www.1and1.com/?k_id=6815038
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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-