Where is the Documentation?
Here is an interesting blog post from Dave Nicolette, about the absence of documentation in agile software development.
I'm not quite sure where the eggplant parmesan comes into it! I think Dave might have been drinking :-) Nevertheless it's an interesting and thought-provoking article.
In my opinion, some lightweight documentation helps to bring structure to people's thinking, and obviously helps to share important information between people in the team. But it becomes counter-productive when it goes over the top, which sadly is all too common in software development!
That's why I love User Stories for capturing requirements. They add structure to the process. But keep things lightweight and simple.
Kelly.
P.S. Click one of the icons below to join the growing community of people keeping up with this blog by RSS or by email...
I'm not quite sure where the eggplant parmesan comes into it! I think Dave might have been drinking :-) Nevertheless it's an interesting and thought-provoking article.
In my opinion, some lightweight documentation helps to bring structure to people's thinking, and obviously helps to share important information between people in the team. But it becomes counter-productive when it goes over the top, which sadly is all too common in software development!
That's why I love User Stories for capturing requirements. They add structure to the process. But keep things lightweight and simple.
Kelly.
P.S. Click one of the icons below to join the growing community of people keeping up with this blog by RSS or by email...
20 January 2009 02:10
I highly recommend reading Agile Documentation: A Pattern Guide Lightweight Documents.
http://www.amazon.com/Agile-Documentation-Producing-Lightweight-Documents/dp/0470856173
Documentation can be agile, but as you said, more often than not it is not.