Modern Enterprise Architecture: architecting for outcomes "Modern Enterprise A..."
summary
Claims that many legacy EA practices no longer work and proposes five concrete practices labeled ABCDE: continuous alignment (use Conway and reverse-Conway thinking to reshape teams and systems), architecting for better value sooner safer happier outcomes, continuous architecture with automated policy and decisions pushed down, practicing DevOps at enterprise scale with a tiny CoE and conversational governance, and curating evolution using fitness functions (e.g. ratio of asynchronous to synchronous calls, number of two-pizza teams per feature). Argues that architecture review boards are an anti-pattern and recommends observability tools like Dynatrace, Elastic, Prometheus and Grafana.
AI-written summary · about
chapters (13)
- 0:00Introduction and background
- 1:25Modern enterprise architecture
- 4:49Growth mindset vs fixed
- 6:11Evolution of software delivery
- 8:54Managing enterprise complexity
- 11:40Alignment and Conway's law
- 14:58Team topologies and autonomy
- 17:57System of systems at scale
- 20:51Architecting for outcomes
- 24:56Continuous governance
- 29:45DevOps at enterprise scale
- 32:10Evolutionary architecture
- 36:07Q&A and closing thoughts
related talks
38mModern Enterprise Architecture: Architecting for Outcomes
50mEnterprise Architecture = Architecting the Enterprise
40mIs it possible for enterprise architects to be really agile?
33mBuilding Evolutionary Architectures
40mArchitecture Modernization: Aligning Software, Strategy, and Structure
42mBuilding Evolutionary Architectures: Principles and Practices
34mEnterprise Architecture and Organizational Agility
30mEA Today and in the Future