I am looking for a clear set of Acceptance Criteria for project and system documentation to include in our ‘standard’. With criteria I mean an objective ‘measurement’ that the delivered documentation complies to the expected quality.
For specific project management documentation I can use a standard Table of Contents.
I have more problems with User documentation and Manuals. What makes a good manual? How can I prevent that a manual is useless for easy use but the vendor argues that everything is included (for instance, just summed up).
Same goes for technical installation docs, development documentation (how can I ensure that somebody from outside the vendor can also read this, if we want to have additional development done by somebody else – internal or external), etc.
Thanks in advance
Steph
