| Resolved Traditional methodologists are a bunch of process-dependent stick-in-the-muds who'd rather produce flawless documentation than a working system that meets business needs. Rebuttal Lightweight, er, "agile" methodologists are a bunch of glorified hackers who are going to be in for a heck of a surprise when they try to scale up their "toys" into enterprise-level software. | “Today, a new debate rages: agile software development versus rigorous software development.” Jim Highsmith, Guest Editor Opening Statement Agile Can Scale: Inventing and Reinventing SCRUM in Five Companies Agile Versus Traditional: Make Love, Not War! Business Intelligence Methodologies: Agile with Rigor? Agility with the RUP Extreme Requirements Engineering Exclusion, Assumptions, and Misinterpretation: Foes of Collaboration | |
| Next Issue The Great Methodologies Debate: Part 2 Guest Editor: Jim Highsmith Is the RUP really "rich and light"? Can a self-described "spy" in the house of agile turn double agent? And why would one of the agile movement's foremost proponents confess that "agility shows up in the execution -- or it doesn't"? In the January 2002 issue, we'll continue our methodologies debate with articles by such luminaries as Ivar Jacobson, Stephen Mellor, and Alistair Cockburn. Tune in next month for more lively opinions from both sides of the methodological divide. | ||
Resolved: Traditional methodologists are a bunch of process-dependent sticks in the mud who'd rather produce flawless documentation than a working system that meets business needs.
Rebuttal: Lightweight, er, "agile" methodologists are a bunch of glorified hackers who are going to be in for a heck of a surprise when they try to scale up their "toys" into enterprise-level software.
Ah, come on -- we're not that far apart, are we? In the December 2001 issue of Cutter IT Journal, we begin our debate on agile vs. traditional methodologies and see where there are true differences and where we can find common ground. Can traditional methodologies handle change? Can agile methodologies scale up? Do traditional methodologies put people last? Are there problem domains where agilists should fear to tread? Pack your opinions and come along for the ride!
