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.
Subject:Estimating Online Help Schedule From:emmy_aricioglu -at- hp -dot- com To:TECHWR-L -at- LISTS -dot- RAYCOMM -dot- COM Date:Tue, 28 Mar 2000 14:59:57 -0800
I've been assigned to my first online help project and
need to deliver a development schedule to the team. The
(software) product is new, to be released August 1, and
the GUI may not be ready at the release date. If the GUI
is not ready, the product will need command line help. I'm
assuming now that I will just do the best job possible under
the circumstances and that opportunity to perfect (or actually
create) the online help will be available at next release.
I'm wondering if those of you experienced in this type of
situation would care to share your project schedule with me.
How do you estimate how long it will take to create online help
(as I've defined above)? Do you count backwards from the release
date to find your "begin development" date? Or do you have a
firm development schedule that you adhere to and then use other
tactics to manage expectations, if you get my drift <g>?
