It may be my narrow experience, but most Agile teams I encounter develop few to no diagrams or high-level views of the architecture they’re implementing. Instead, they allude to “being Agile,” where architectural docu­mentation is unnecessary, which implies that you simply collaborate around the code and magic (emergent architecture) occurs. In this Advisor, I suggest documentation as a good tool for striking the right balance between architecture and agility.