Create Minimal but Sufficient Documentation
When documenting requirements, design, and architecture, keep it light.
Documentation is a means to an end—it’s a tool to guide, facilitate and communicate decisions. Planning the documentation should begin with those ends in mind. More is not necessarily better. When documenting requirements, design, and architecture, keep it light :
Favoring models over documents – When applied properly, models can provide more easily maintained ways to manage, especially in a continuous change environment.
Keeping documentation collaborative – Many team members participate in the creation, feedback, and refinement of solution intent information. Ensure their work is included.
Documenting items in only one place – Record any requirements and design decisions in one place, a single source of truth that serves as the repository of record for everyone and everything.
Keeping it high level– Document at as high a level of abstraction as possible, and don’t over-specify. Describe solution behavior with intent, not specificity. Decentralize requirements and design decisions.
Keeping it simple– Record only what’s needed. Less is more.