Agile Architecture | Agile Transformation
Lean Architecture Principles: Wrap up! Sander van den Berg 11 Aug, 2010
Questions about whether design is necessary or affordable are quite beside the point: design is inevitable. The alternative to good design is bad design, not no design at all. — Douglas MartinAlong came the DevOps transformation focusing on merging Development and Operations practices so that the teams could take full responsibility for what they built. And as a bonus, it also brought in the architecture capabilities, which helped move the teams in the right direction. And it also removed much responsibility from the architects to the teams. Like what we observed in an agile transformation, architects are left out, which does not mean we do not need them.
Different levels of work have as different a nature in terms of modes of thinking as, by analogy, water is different to steam – Elliott JaquesArchitects should still be dealing with all the different levels of scope as they did pre-agile, to quote Gregor Hope, ‘ride the architecture elevator.’ The difference in agile Architecture is that architects now need to take the lead in new opportunities and then continuously shift the responsibilities to teams and managers. We can do this through participatory design. We collaboratively model the solutions with stakeholders, users, and teams. However, this requires a new set of capabilities of an architect. These capabilities are more focused on the social domain than the technical.