All Methodologies Devolve

Posted by Robert Merrill on February 1, 2009 under Agile Methods | Be the First to Comment

When software methodologists argue, they usually assume the proper application of their favorite. Unfortunately, in the real world, methdologies are seldom applied as their advocates intend.

Waterfall devolves to a “team” of isolated individuals, specialized by role, each accountable to a different manager, producing a very high ratio of paper to software. And the latter is late, over budget, sort of what the buyers asked for, and doesn’t deliver nearly as much value as promised in order to get the project funded.

Agile devolves to “Cowboy Coding,” producing brittle software that addresses a particular problem, but un-supportable and un-extensible except by the cowboys. They’re the only ones who can comprehend the design. Documentation? “We’re agile—we don’t need no stinking documentation.”

I’ve done Cowboy Coding (what a rush, until you have to support your creation), I’ve done Waterfall, and I’ve done Agile. And I’m convinced Agile is usually the way to go. Why? Unlike Waterfall, Agile doesn’t depend on accurate estimates, provides early feedback of trouble to both buyers and developers, and doesn’t produce a lot of scaffolding and waste.

The fact is, people make mistakes as well as software. Agile doesn’t deny the human factor or attempt to manage it out of existence, it leans into it. As long as you leave Agile’s load-bearing walls intact, you’ll stay safe, have fun, and deliver value through software, pretty consistently. For a simple example, with numbers, of why it works, check out A Tale of Two Processes on WTN.