Register or log in to access this video
In the sociotechnical system that is software development, software architecture plays a crucial role.
We strive to design our systems in a way that allows us to scale, both technically and organizationally. In a way that allows a fast flow of change. Succeeding in doing so will be a significant competitive advantage. But how do we ensure we follow the right architecture principles across the organization, in times of empowered teams and extreme ownership?
Lutz talks about the importance of a strategic approach to software architecture, that prevents teams from becoming architecture firefighters, who spent an excessive amount of energy applying short-term fixes to architectural problems. He explores the options to implement architecture strategy in a modern software development organization that is built on value stream aligned teams. Developers in such organizations will flat-out reject any “ivory tower architects”, or needing approval of architectural decisions by some governance body – and rightfully so. Having experience as a software architect, as a manager of an “enabling team” of architects, and as an engineering manager in setups with no designated architects at all, he shares his learnings and provide some heuristics on which approach to choose when.
