Agile and architecture, finally friends after 15 years

The term 'software architecture' has historically induced visions of ivory tower architects doing big design up front in order to create excessively detailed documents, delivered to an unsuspecting development team as if they were the second leg of a relay race. 2001 saw the creation of the 'Manifesto for Agile Software Development', a turning point for the software development industry that put focus back upon individuals and interactions, working software, customer collaboration and responding to change. Big design up front certainly has problems but, in the haste for agility, some teams threw the baby out with the bath water. Big design up front was replaced with no design up front, documentation was seen as redundant, speculation became YAGNI and a new wave of 'agile architects' (who, of course, didn't call themselves architects) delayed decisions until the last responsible moment. Although agile and architecture may have parted ways, they are finally friends again after 15 years. This is their story.

Other formats

PDF


    of 102