Depending on the audiences/perspective one can explain an application or architecture using UML diagrams like sequence diagram, component diagram, interaction diagram etc. DevOps teams deal with multi-interconnected processes. How would one explain their work/dependencies to various stakeholders like developers, managers, enterprise architects etc? What kind of tools they use for team collaboration? What kind of best practices are used to identify and fix the gaps?
My $0.02 -- some of the best tools, IMO, are collaboration, direct communication, and feedback through continuous use and experimentation. I think that those who understand DevOps quickly find that you need very similar mindsets to have effective agile development practices as you do to have effective DevOps practices. One thing to note is that the Agile and DevOps communities have formed / are forming partnerships and many of the folks who adopt Agile and do so successfully naturally extend their practices to include DevOps. In fact, one of the keynote speakers in the last Agile conference I attended was Gene Kim, author of the "Phoenix Project" which is the DevOps equivalent of Goldratt's "The Goal".