Without Focus on Product and Team, Your Product Falls Flat

Software architects thrive on their love for software architecture. While this is neither surprising nor wrong, software architecture must serve a purpose beyond itself. This purpose is product success, and software architecture and team structure are the basis for and essential in enabling this success. In this talk, we will explore the crucial role of the product concept and team structure and how they help achieve architectural success.
You might want to think: this is self-evident, so why a session about it? Look around you? Do you see development results that don’t create value for your customers? Solutions that are exciting from a developer’s perspective but not for the customer? Teams that struggle with dependencies and cross-team collaboration?
Therefore we need to shift our perspective to the customer’s point of view, continually developing architecture and team structure to improve our product according to the customer’s need. Embracing agile principles, we’ll see how architecture develops alongside product understanding and team organization, adapting fluidly to changing needs.
Join us if you’re ready to rethink architecture in a broader context and stay agile and dynamic as an architect.

Transcript

1. Without Focus on Product and Team, Architecture Falls Flat Software Architecture Gathering Berlin, 2024
2. About Me and This Talk Peter Götz Software Developer Agile Coach & Trainer Continuous Learner & Improver Developing Software Supporting Teams Helping Organisations
3. Background & Foundation
4. From Software Developer to Software Architect Get better at coding Get better at design Software Developer Senior Software Developer Software Architect Software Architecture as a career path?
5. Software Design Software Architecture Instead, Focus on Software Architecture “All architecture is design but not all design is architecture. Architecture represents the significant design decisions that shape a system, where significant is measured by cost of change.” Grady Booch, 2006
6. Twin Peaks Model Bashar Nuseibeh, 2001 Requirements Architecture General Detailed Level of Detail Specification
7. Melvin E. Conway, 1968 Architecture Follows Communication [O]rganizations which design systems (in the broad sense used here) are constrained to produce designs which are copies of the communication structures of these organizations. Conwayʼs Law
8. Value-driven Product Flow
9. person with a problem we can solve Customer for them for us for us all Value Deliver Value in a Complex Environment
10. Team(s) Architecture Customer Value Product
11. Team(s) Architecture Customer Value Product FLOW
12. Culture Customer Value Product FLOW Team(s) Architecture
13. Culture Customer Value Product FLOW Hypotheses Measurement Team(s) Architecture
14. Questions? peter@flowdaptic.de https://flowdaptic.de https://linkedin.com/in/petersgoetz/