Be Funky, Be Agile

by TS on January 18, 2009

Picture 001Image by pcalcado via Flickr
Agile software development has been around for a while now. An adaptive software development process was introduced in a paper by Edmonds (1974). Notable early Agile methods include Scrum (1986), Crystal Clear, Extreme Programming (1996), Adaptive Software Development, Feature Driven Development, and Dynamic Systems Development Method (DSDM) (1995). These are typically referred to as Agile Methodologies since the Agile Manifesto was published in 2001.
The Agile Manifesto states:

We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:

  • Individuals and interactions over processes and tools
  • Working software over comprehensive documentation
  • Customer collaboration over contract negotiation
  • Responding to change over following a plan

That is, while there is value in the items on the right, we value the items on the left more.

Princeples behind the Agile Manifesto:
  • Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
  • Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
  • Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
  • Business people and developers must work together daily throughout the project.
  • Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
  • The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
  • Working software is the primary measure of progress.
  • Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
  • Continuous attention to technical excellence and good design enhances agility.
  • Simplicity–the art of maximizing the amount of work not done–is essential.
  • The best architectures, requirements, and designs emerge from self-organizing teams.
  • At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
As of today most of the companies I know develop software according to the agile philosophy but with different flavors of the above methods. During the last few days Scrum has been popping out on different occasions, so I decided to find out a bit more about it.
Scrum: Agile For Everyone

View SlideShare presentation or Upload your own. (tags: management scrum)
and I also found a really good video about agile development at Google:
Agile development feels pretty much natural to me and I can’t really imagine how a team could be fast enough in a different way. The Agile Manifesto is very customer oriented and that is how it should be :)

Enhanced by Zemanta

2 comments

Nice overview.

It’s interesting how, whenever things get a little rough, this agile approach morphs back down to waterfall with everyone oblivious to what’s going on.

Hence the role of chief agile kicker / whip wielder :).

by Tadej on 19/01/2009 at 08:35. #

[...] January the decline of Funky.Karaoke started I summed up some knowledge in a post about Agile. I have also been to [...]

by Two and counting : Funky.Karaoke on 27/07/2009 at 20:33. #

Leave your comment

Required.

Required. Not published.

If you have one.