Every document has a reason for being. It is intended to be read by a specific audience. It is intended to convey a specific understanding. It is not just a check mark on the project plan. And it should not go to SharePoint to die.
We will evaluate some of the common documentation practices, and see if we can justify each document. Most will be revised. Some will be discarded. A few will be added. This process will minimize the cost of documentation, and maximize its value.
What should be in this document? Who is going to read it? When should we write it? Justify each document, and they will add value to your project.
Sign in to add slides, notes or videos to this session