Documentation

The (Project) Documentation subject focuses on documents created during and for the project itself. Some of these documents may end up in the product configuration documentation (see the subject "Configuration Management" for a more in-depth discussion of managing the product definition documentation over the lifetime of the product) while other documents make their principal value contribution only during the project itself and have only archival value once the project has been completed.

What are the crucial documents that should be generated for a development project? When should the documents be created? Where can I go to find examples? I'm an experienced project manager, but the project documentation that I create just seems to gather dust and never gets used during the project. How do I "animate" my project documentation so that it is truly useful in controlling and guiding my project?

• Click here for Burning Questions and know-how on Documentation