Post Tagged with: "agile"

This year’s NCAA national football championship was won in dramatic fashion by the University of Alabama. 

Most remarkable was that the game was actually a tale of two halfs. The first half was dominated by the Georgia Bulldogs, and the second by the Alabama Crimson Tide.

Alabama’s coach Nick Saban recognized that they couldn’t win doing what they’d been doing in the first half. At halftime, he brought in freshman quarterback Tua Tagovailoa. Saban felt Tagovailoa would have a better chance given his superior passing game. It was risky, but Saban felt he wasn’t going to win by doing what he’d been doing. 

In the software development world, this process of trying something, seeing what happens, and then adjusting accordingly is known as agile development. 

What’s agile development got to do with Oprah Winfrey?

[caption id="attachment_2070" align="aligncenter" width="650"] Pair programming, an agile development technique used by XP (Lisamarie Babik/Wikimedia).[/caption]

In the 1990s and early 2000s something happened in the software development world, something that wasn’t good. Software development fell victim to the bean counters and micromanagers of the world and followed a project management script known as the “waterfall method.” The waterfall method was fine for projects that were simple and well-defined, but many many software projects fell out of this realm with either changing requirements, or trying to understand new technology—or sometimes both at the same time.

As a result, many software development projects in the ‘90s were organizational nightmares. Much of the purpose of developing software to begin with (i.e., why are we building this?) was lost as organizations devolved into procedural nightmares and territory fights.

This is the short story of the agile revolution—a term you may have heard of. But you probably didn’t realize was a cultural revolution.