Honestly, I was not aware about this myth that Agile means no documentation so I personally did all documentation which I used to do in normal circumstances. Diagrams, references, steps and scripts all were documented properly for all activities. However I must admit that I came across this myth in one of the Daily Scrum where someone pointed out that No documentation in Agile. It is a MYTH.
Though, I hardly remember anyone else working on the documentation but it was in initial period. Other kind of documentation such as Architecture Document and coding standard was done in Design phase only but after that phase it took a back seat. However, the moment application was in good shape, documentation was desired.
For example, we create different kinds of scripts to automate infrastructure in the cloud environment. In such cases, it is important to maintain versions of scripts, keep documentation on how to execute that script and how it works. It is also important to document configuration and other setting required based on the environment. It always helps in future to get back to original configuration or in case of troubleshooting. It also helps in keeping track with the changes or enhancements in the different sprints.
Free Agile Scrum Cheat Sheet & Handbook:
|The Essential Scrum Cheat Sheet||Free Cheat Sheet:Agile Adoption||Free Scrum Master’s Handbook|