Summary

The playing field for architects has been challenged severely due to the mismatch between traditional ways of architecting and Agile architecture. Elements of the ivory tower, astronauts, and policing behaviors compounded with perceptions and economic considerations added fuel to the no-architect movement that surfaced with Agile software development. As we learned, it is vitally important to have dedicated or designated architects in Agile teams.

While collaboration is an extreme necessity, Agile architects must be substantially and equally strong in technology, domain, leadership, and strategy. The conventional metaphors of a construction architect to a gardener, elevator, sous chef, and interior designer need a radical transformation. The ability to know the unknowns, be prepared to adapt, pave the way for developers, prioritize the technical backlog, timing architecture decisions, and have a solution mindset with system thinking are paramount for Agile architects.

...