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.
> The quality goals for the beta version of the documentation depends on
> business, marketing and technical goals of the beta program for this
> particular product release ...as well as the type of and audience for
> product. That is, there isn't as simple generalization.
I agree. But that said, when pressed, my boss and I tell people we're aiming for beta docs to be 60-75% complete.
And I try to emphasize that tech pubs sees a beta test as an opportunity to test the docs and get valuable feedback on them -- what's missing, unclear, incomplete, etc. -- just like the developers hope to get valuable feedback on the application.
Sometimes we actually do get good feedback! :-)
Richard G. Combs
Senior Technical Writer
richardDOTcombs AT polycomDOTcom
rgcombs AT gmailDOTcom
Use Doc-To-Help's XML-based editor, Microsoft Word, or HTML and
produce desktop, Web, or print deliverables. Just write (or import)
and Doc-To-Help does the rest. Free trial: http://www.doctohelp.com
Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at: http://www.ModernAnalyst.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-