You are here:
Tuesday, September 22, 2009
Agile Versus Everthing Else
You have to be a member to view this video.
The great minds of software management are holding their heads these days over the questions of waterfall versus Agile, and architecture versus Agile, and everything-else-old-fashioned versus Agile. Most such reflections, and certainly the discussions surrounding them, are unbelievably misinformed. In this talk I look at how the traditional waterfall cycle is at the foundation of Scrum, and why up-front- thinking thrives as a foundation of Scrum in activities such as up-front architecture. I'll also describe how Agile fixes the fundamental stovepipe flaws and long, isolated work intervals that are popular in most management applications of waterfall. I'll also give a vision of how activities that take months in waterfall can take days in Agile, and explain why. Last, I'll explore how the human philosophies of these two schools of product development may, or may not, differ-in fact, both of them have elements of micro-management, and both for the same reason: predictability.
Jim Coplien
Jim ("Cope") Coplien is a Software Architecture and Agile Consultant at Gertrud & Cope in Denmark. He has a 25-year history as an "early adopter" and innovator behind several strategic innovations in software: his C++ Idioms book was one of the major sources for Design Patterns; his work on Organizational Patterns was one of the foundations of the structural components of XP and was the inspiration for Scrums.
Members have the ability to post comments for webinars.
