What do you do when your budget gets slashed, your headcount is dropping, and your deadlines don’t relent? When there just aren’t enough resources to design high-quality software, but you still have to deliver? Redefine the criteria for success! Agile programming to the rescue!
We don’t need no stinkin’ requirements! We don’t need no stinkin’ design sessions! Heck, we don’t even need testers, just ship the customer the daily build and let them sort it out. They’ll be so utterly disgusted with the initial attempts at the product that they’ll be fawning all over the final release, even if it’s not much different from what they got at the first attempt. Make them suffer along WITH you!
Besides, that’s what we’ve been doing anyway, ever since the tech bubble burst. We haven’t had time for all that other fancy-pants stuff. We’re just finally acknowledging it. With a vengeance.
———-
And the stuff that “The Agile Method ™” gets right… small iterative steps, smart design and decomposition, concise variable naming… well… no duh.
[Yawn] Wake me up when the next hot fad has something truly new and useful to offer…
Cara: Agile is another word for: disorganized desperate baseless slipping on of responsibility to people who are already burdened, and, I would venture to guess, don’t really care passionately about the end goal. I mean, how does it benefit you guys? Question for the ages.