Agile Documentation

Working software over comprehensive documentation.[¹]

Implies that the code should reflect the business requirements. Let’s focus on the code. Let’s keep the software working. Writing code is more productive, but documentation is needed, as everybody suggests.

The answer I don’t get is why documentation at the code level is needed. Formalized requirements processes can map the concept from the business into the code and vice versa.

The Ubiquitous Language is a shared language developed by a team composed of domain experts and software developers. [²]

—

[¹]: Agile Manifesto (https://agilemanifesto.org/)

[²]: Vaughn Vernon (2013): Implementing Domain-Driven Design (https://www.amazon.com/Implementing-Domain-Driven-Design-Vaughn-Vernon/dp/0321834577)