RE: RE: 2 weeks !

[Susan W. Gallagher <sgallagher5 -at- cox -dot- net>]

Actually, John, that estimate also includes chasing after
SMEs and/or rebooting your machine every time the beta
software crashes as well, and in my experience, the software
documentation estimates she gives of 4 to 5 hours per page 
-- including the project management, writing and editing, 
replacing the screengrabs for the umpteenth time, doing the 
publication edit, reviewing the proofs, ... -- is pretty 
much right-on ->for a *typical* doc group with varied skill levels<-. 

I haven't worked with hardware much, so I really couldn't 
say whether it takes that much longer.

-Sue Gallagher

> 
> From: "John Posada" <JPosada -at- isogon -dot- com>
> >While I fully appreciate everything you 
> >said, I still think it would be very difficult 
> >to convince anyone outside our profession to give 
> >us an 8hr/pg timeline. 
> 
> I wonder if that figure isn't reasonable.
> 
> OK, I don't think many of us need 8 hours to write a page of
> instruction...takes me maybe 2-3 hours to create a detailed page of
> steps.
> 
> However, add in:
> 
>...



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

SEE THE ALL NEW ROBOHELP X5 IN ACTION: RoboHelp X5 is a giant leap forward
in Help authoring technology, featuring Word 2003 support, Content 
Management, Multi-Author support, PDF and XML support and much more! http://www.macromedia.com/go/techwrldemo 

>From a single set of Word documents, create online Help and printed
documentation with ComponentOne Doc-To-Help 7 Professional, a new yearly
subscription service offering free updates and upgrades, support, and more.
http://www.doctohelp.com

---
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- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit
http://www.raycomm.com/techwhirl/ for more resources and info.