Brandon,

Thanks for commenting.

The maintenance of documentation is not a small task. I am going to tackle it, by setting up reminders to re-visit certain topics at least yearly.

Although it is not the most exciting task, keeping documentation updated is a valuable task. Minimally, when Sitecore releases a new major feature or product line, I think it would be beneficial to our customers to review and update their training, wikis and product roadmaps in light of the new announcements.

I always have to laugh when I hear comments like, “Contrary to most organizations’ Agile practices, there is still a need for documentation.”

It’s like, “well, of course there is!” But you are correct that it is not always well established or maintained. Classes on Agile should always remind the students that just because the Agile process doesn’t have it defined, doesn’t mean that your team doesn’t still need it — or deserve it. I’ve been in Agile classes where the instructor mentions documentation as an example that is still good to do. Or project charters… etc. etc. Agile doesn’t say NOT to do these things, so if they are helpful to your group, by all means, do them!