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.
I work for an Internet service provider in the engineering division which
has numerous departments (programming, system administration, network
engineering, etc.), all with different products, schedules, projects,
release issues, etc. The doc group has been asked by the VP to create a
"standardized" "Product Release Checklist" to be used across the board by
the entire division to ensure that each department necessary to a project
has been involved, and that all i's have been dotted and t's crossed. We
haven't done anything like this before, and while we have several ideas of
how to attack this, any advice that people have could prove invaluable.
Has anyone out there produced a "standardized" "Product Release Checklist,"
and if so, can they share it?
