If you find this site useful, you should try my 55-page eBook here

Where is the Documentation?

by Kelly Waters

Email This Post Print This Post Save As PDF
agile documentationHere 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...
keep up by rss feedkeep up by email

  • Digg
  • del.icio.us
  • StumbleUpon
  • Yahoo! Buzz
  • Technorati
  • Facebook
  • TwitThis
  • MySpace
  • LinkedIn
  • Live
  • Google
  • Reddit
  • Sphinn
  • Propeller
  • Slashdot
  • Netvibes

1 comments:

  1. David Carver said...

    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.

10 Key Principles of Agile Development

How To Implement Scrum in 10 Easy Steps

User Stories - Agile Requirements

Agile Project Management

10 Key Principles of Agile

How To Implement Scrum

Most Read

Agile Leadership

Agile Requirements - User Stories

Agile Estimating

Agile Testing

Agile Project Management

Lean Software Development

Agile Teams