Panel
summary
Panel surfaces concrete wins and hard lessons: use team topologies with Wardley mapping and bounded contexts to split systems, keep architecture decisions in public architecture decision records, and run short experiments like TDD workshops with external coaches. Concrete numbers and moves matter — moving 500 people to create a new culture, running ten hard TDD cases to prove change, and tracking DORA metrics to spot gaming. Practical guidance covers dynamic reteaming, domain training, and when to spin up a separate unit to execute a five‑year transformation.
AI-written summary · about
chapters (13)
- 0:00Introduction and panelists
- 2:35Emergent themes from the day
- 5:24Changing architecture vs organizations
- 16:44Agile teams in rigid organizations
- 20:18Avoiding over-architecture
- 24:07Inverse Conway maneuver
- 28:42Enabling teams for architecture
- 33:12Gaming metrics and outcomes
- 37:50Bridging agile and architecture
- 42:06Maintaining agility while growing
- 46:29Fear in agile adoption
- 54:35Mindset change vs leveraging diversity
- 59:51Closing remarks and thanks
related talks
41mWhy one model can’t fit all creating fulfilling engineering organizations
42mPanel Discussion: Architecture
58mTeam Topologies Panel
40mPractices from trenches for embracing evolutionary architecture in wild
48mCase Study: Tools and Strategies for Tackling Legacy Practices
35mGuiding teams, and shaping a portfolio using Wardley maps & DDD
19mWrap: What To Build Next
25mHow to Drive Cross Team Techincal Changes