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 Scenario:
I have been given a document which is around 6 months out of date and it
needs to be updated. This document is a Programer's Manual and the
developer associated with it has left our company leaving behind a 63
page C code after making lot of changes in the past six months.
The Requirement:
I need to submit a plan with details upto the last level of tasks
involved in updating this document along with start and end dates for
each tasks
The Problem:
How do I tell what are the last level tasks that I will be doing even
before I understand what needs to be changed in the document? I know the
higer level tasks like
1. Understanding the code (Very difficult, any suggestions on how to go
about it?)
2. Making necessary changes to the Manual
3. Review
4 .Rework
5 .Sign off
