Documentation in Agile

We value “working software over comprehensive documentation”. That is, while there is value in documentation, we value working software more. This prioritisation helps us get things done and avoid waste. However, both extremes are very common out there in the wild, development teams who avoid documentation altogether (“our code is self-documenting”), and teams who create way too much documentation. This talk is about the spectrum between those two extremes – as a Lead Developer, how do you find ways to leverage documentation as a means to make communication in the team more efficient, and align everybody to a common picture of the system they are building, without creating too much waste?