Agile Methodologies

There are various agile methodologies, although ‘agile development’ is really a philosophy, not a methodology.  A set of values and principles.  The agile manifesto describes these values and principles, and I have also written about 10 key principles that underly most agile  methodologies.

Agile methodologies are characterised as ‘agile’ when they exhibit these principles.  Some examples are:

  • Scrum - which focuses on agile management and on how to better organise development teams.
  • XP (Extreme Programming) – which includes  some management elements but emphasises technical practices more and is therefore more of an agile engineering methodology in my mind.
  • DSDM – Dynamic Systems Development Method, one of the earliest iterative development methods.
  • Lean Software Development – which focuses on cutting out as much overhead as possible.

These seem to be the most widely adopted agile methodologies, however there are other agile methodologies, for instance:

Information on the web about these agile methodologies seems a little scarce, however I did find this overview of agile methodologies quite interesting.

If I’ve missed any, please feel free to add them in the comments, or let me know what you think of these methodologies…

Kelly.

2 Responses to “Agile Methodologies”

  1. Kelly, I actually wrote a book about the “major” agile methods in 2002 (so it’s getting a little dated now). The title was “Agile Software Development Ecosystems.” The best part, for me, was interviewing and writing about the authors of these methods.

  2. Kelly Waters says:

    That’s pretty cool Jim, I wish I’d written a book! Do you think the landscape has changed much since then?

Leave a Reply

What is 3 + 10 ?
Please leave these two fields as-is:
Please do this simple sum so I know you are human:)

There are 101 ways to approach anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”

DAN PULHAM, DIGITAL DIRECTOR
TELSTRA