Evaluating software documentation projects quickly

Often when we start a new job, or are dropped into an existing software documentation project at our current job, getting up to speed is overwhelming. This article suggests steps to quickly assess the situation, develop a plan, and begin writing.

Text by Nicoletta A. Bleiel

Inhaltsübersicht

Evaluating software documentation projects quickly

Learn the landscape

First, you need to find out the background of the project – its state, the team, and the documentation standards used.

Project status
Most software projects will fall into one of these seven categories:

  • A new product that is still in development, with no user documentation
  • A new product that is complete (or nearing completion), with no user documentation
  • An existing product with little documentation
  • An existing product with documentation
  • An existing product that is in transition to new user interface or other major change
  • An existing product in maintenance mode/New version in process
    Product is in maintenance mode

You need to find out what category your project fits into, and also what specifications or requirements exist (if any). Verify with subject matter experts (SMEs) that those documents are up-to-date.

If any end user documentation exists, you ...