To be Agile affords organizations the opportunity to build quickly and respond to change--I get that. I find there are many misconceptions about documentation, Some folks state that the Agile Manifesto de-emphasizes it and therefore its really not necessary. Depending on your industry though, documentation (planning, Design, etc.) may be an important for compliance or other reasoning. Interested to hear some feedback on this. Saving Changes...
Sort By:
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
There is a big misunderstanding about agile. I am not saying that for your post above just because I am working with Agile from 1995 and each time some organization hire to me for helping them I spend lot of time trying they understand that agile is not faster delivery, is not cost reduction, is not respond faster to change unless the whole organization is ready for that (architecture), is not a mindset only, etc etc. The other missunderstanding is about the Manifesto which first, is for software and second people forgot to read the paragraph: "That is, while there is value in the items on the right, we value the items on the left more" Third people forgot to read what is stated in the link "About the Manifesto" mainly in paragraph number 9: " The Agile movement is not anti-methodology, in fact, many of us want to restore credibility to the word methodology. We want to restore a balance. We embrace modeling, but not in order to file some diagram in a dusty corporate repository. We embrace documentation, but not hundreds of pages of never-maintained and rarely-used tomes. We plan, but recognize the limits of planning in a turbulent environment. Those who would brand proponents of XP or SCRUM or any of the other Agile Methodologies as "hackers" are ignorant of both the methodologies and the original definition of the term hacker. " Saving Changes...
This is one of the more common faux agile or fr-agile anti-patterns. Documentation needs to be fit for purpose and minimally sufficient. Anything more is waste, but anything less might create longer term waste and/or violate regulations.
The form that documentation takes should be assessed to determine whether it is the most effective for short and long term needs. For example, a standalone document might be easy to create but is hard to collaborate on over time as compared with a living wiki.
