I'm writing a document describing process improvement recommendations. I have some best practices I've learned so far. I use those practices most of the time. But I suppose there are other ways to approach the task of writing formal process description document.So, how do you usually structure your documentation? As you could already find out, I'm especially interested in structuring formal process description documents which are usually created by QA and sometimes Project Managers. What sections should it contain?My documents usually contain following sections:ContentGoal ScopeTerms and abbreviationsInputsProcess descriptionArtifactsOutputsWhat else should there be? Did I forget something? Are there other approaches for structuring formal documents? Link to best practices descriptions are greatly appreciated.
How to structure process description documentation?
development process;documentation;qa;technical manuals