5b14a17c_for_Agile_Software_Development__2
[0] Project overview [1] Developers, Managers, Maintenance Developers, Operations Staff [3] I typically create and maintain this document during development. Keep it short and to the point, I don't ever remember one getting beyond ten printed pages and most are less than five. This document serves as a starting point for anyone new to the team, including maintenance developers, because it answers fundamental questions that they are likely to have. Whenever you first share this document with anyone ask them to keep track of major issues that they were not able to easily resolve using this document, or any misinformation they discover, to provide insight into potential updates for the document. I often call this a "Good Things to Know" document. [4] Yes [2] 
A summary of critical information such as the vision for the system, primary user contacts, technologies and tools used to build the system, and the critical operating processes (some applicable to development, such as how to build the system and some applicable to production, such as how to back up data storage). Also provides references to critical project artifacts such as the source code (the project name in the source code control system is often sufficient), where the permanent models pertaining to the system (if any) are, and where other documents (if any) are.
Agile/Lean Documentation: Strategies for Agile Software Development
2