Agile Methodologies

By xerocube | May 25, 2007

You come to work and are greeted with a new software project to complete. But, seeing as the last project ran over budget, the engineers worked long hours, and the project never hit the actual requirements; management has mandated that your team will be using an Agile methodology. The theory being, you’ll have a small team, able to communicate easily with each other, don’t have to be bogged down by documentation, able to adapt to a change quickly, and still produce a working piece of software.

Sound familiar? I’ve been in several situations like this and they are never what they are cracked up to be. I’ve struggled to come up with a good analogy to explain the differences between an Agile methodology and a more structured methodology, like Waterfall, evolutionary, or RUP.

Luckily, for us, Worse Than Failure posts an article defining the Great Pyramid of Agile.

The Great Pyramid of Agile – Worse Than Failure

Two pyramid builders – Goofushotep and Gallanthotep – set out to construct a pyramid for their pharaoh. Being the traditionalist that he was, Goofushotep build the pyramid from the ground up and risked not finishing it before his pharaoh’s death. Gallanthotep, the Agile architect, built a small pyramid first and built additions sideways, so that there was minimal risk in having an unfinished pyramid when his pharaoh died.

Of course, this is just a sampling of the article. Rush on over and read the full story, plus more tidbits about the nature of Agile.

Topics: Quality Assurance, Tech | No Comments »