Saturday, May 7, 2011

"Agile Manifesto" and learnings from "The CAthedral and The Bazaar"

Came across the 12 principles behind Agile Manifesto.
  1. Customer satisfaction by rapid delivery of useful software
  2. Welcome changing requirements, even late in development
  3. Working software is delivered frequently (weeks rather than months)
  4. Working software is the principal measure of progress
  5. Sustainable development, able to maintain a constant pace
  6. Close, daily co-operation between business people and developers
  7. Face-to-face conversation is the best form of communication (co-location)
  8. Projects are built around motivated individuals, who should be trusted
  9. Continuous attention to technical excellence and good design
  10. Simplicity
  11. Self-organizing teams
  12. Regular adaptation to changing circumstances
I could not stop wondering how they resemble with various points highlighted in "The Cathedral and the Bazaar" by ESR
  • Good programmers know what to write. Great ones know what to rewrite (and reuse). [point 2 above]
  • “Plan to throw one away; you will, anyhow.” (Fred Brooks, The Mythical Man-Month, Chapter 11) [point 2 above]
  • Treating your users as co-developers is your least-hassle route to rapid code improvement and effective debugging. [point 6 above]
  • Release early. Release often. And listen to your customers. [point 3 above]
  • Every good work of software starts by scratching a developer’s personal itch. [point 8 above]
  • Smart data structures and dumb code works a lot better than the other way around. [point 10 above]
  • Often, the most striking and innovative solutions come from realizing that  your concept of the problem was wrong. [point 12 above]
     


No comments:

Post a Comment