Problems with traditional documentation

User and reference manuals are usually scheduled, if at all, for the end of a project. The logic is that there is no point writing documentation until the product is complete – or it will only become out-of-date.

And then the creation. Document writers have to learn the running software without the benefit of documentation and often after key personnel have left the project. Often the technical writer is also a technical tester. The process is akin to archeology.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s