The misguided, CASE-heavy practices of the 1980s fueled the proto-Agile rhetoric of the 1990s and survived full-force into the advent of Agile practices such as Scrum and XP in the past decade. Part of that rhetoric has been to go as far from the sins of the 1980s as possible by discarding up-front requirements (instead we have a promise for a future conversation between a developer and a customer) and architecture (instead, we have had a succession of short-lived ideas including "metaphor" and TDD).

Experience and recent research have both borne out the value of architecture in software development in general, as well as its value in sustaining high velocity and change resiliency in Agile projects. In this talk, Agile expert Jim Coplien will provide tips for putting architecture back into your Agile project without dragging it back into the dark ages -- and all within the framework of the Agile Manifesto.