Concrete strategies for using minimalism in an agile development environment

In my post from last month about Why minimalist documentation is not always a good match for agile development, I explained the issues with using minimalism in an agile environment but was unable to offer any advice on how to effectively use a minimalist approach in an agile shop. I was still wrestling with that question myself.

I think I’m now able to answer that question, but rather than do it in an entirely new article, I feel it’s more useful to simply add that information to the above-linked article. Having both the challenges and solutions in one article makes it easier to distribute for discussion among your own team members and other stakeholders. So please see the above-linked article for the full discussion. If you’ve already read that article before today’s date, the new information is in the third section, about mid-way down, titled What are the conditions that make minimalist authoring more possible in an agile shop?