* Don't use page count estimates (doing such shoots
documentation minimalization efforts in the foot).
* Don't use number of developers (productivity between
developers can vary by a factor of up to 100 to 1).
* Do properly partition the work into right-size and
equal-size chunks, determine the time per chunk, and
then multiply through.
* In doing the above step, don't use Use Cases as they
are too poor of an analysis tool for this purpose. A
taboo-to-mention-on-this-listserv method is required.
> Hi all,
> Given that it is the New Year and time for those
> resolutions, I've set
> myself a goal of improving my estimating skills for
> doc projects (time and
> effort). Does anyone know of a good book, training
> course or other resource
> that I can use?
> Thanks in advance,
> Robyn
>
>
__________________________________________
Yahoo! DSL ? Something to write home about.
Just $16.99/mo. or less.
dsl.yahoo.com
Now Shipping -- WebWorks ePublisher Pro for Word! Easily create online
Help. And online anything else. Redesigned interface with a new
project-based workflow. Try it today! http://www.webworks.com/techwr-l
Doc-To-Help 2005 now has RoboHelp Converter and HTML Source: Author
content and configure Help in MS Word or any HTML editor. No
proprietary editor! *August release. http://www.componentone.com/TECHWRL/DocToHelp2005
---
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-
