Maintaining architectural quality on software teams

Good teams and good products go hand in hand. But how does product quality impact the effectiveness of a team? And how do good teams produce high-quality software architecture? Evelyn van Kelle and Yiannis Kanellopoulos explain how developer happiness and high-quality architecture are interrelated and why we cannot engineer the future without empowering developers.

Good teams and good products go hand in hand. But how does product quality impact the effectiveness of a team? And how do good teams produce high-quality software architecture? Developer happiness and high-quality architecture are interrelated, meaning we cannot engineer the future without empowering developers. Evelyn van Kelle and Yiannis Kanellopoulos elaborate on the interplay between social and technical factors when building software architecture. This includes the importance of tight and loose feedback loops, how communication patterns and organizational structures impact architecture, and how to apply best practices for building highly productive software teams. Along the way, Evelyn and Yiannis explain how to make architectural decisions more measurable by integrating 10 practical guidelines for maintainability in a CI/CD pipeline and share the most common pitfalls when it comes to measuring your architectural quality.