Good CoP, Bad CoP: A Community-Driven EDA Transformation
summary
A chaotic landscape of 40+ remote teams and inconsistent event formats becomes a standardized, self‑service EDA in months: a small steering committee (about 7–9 architects, engineers and a manager) runs RFCs and produces reusable templates, naming conventions and guidance; adoption jumps from 5 pilot teams to 50+ teams by making the Event Catalog + CloudEvents schemas the discoverable, required source of truth; team EDA champions drive backlog changes; a notification event compromise wins over sceptics and workshops replace vanity metrics.
AI-written summary · about
chapters (6)
- 0:00Introduction and background
- 5:49Problems with top-down approach
- 10:11Starting the engineering community
- 15:34Community goals and standards
- 22:24Driving adoption and consensus
- 25:57Summary and next steps
related talks
48mEmpowering Architectural Evolution: Governing Event-Driven Solutions
54mCommunities of Practice – the Not-So-Hidden Force in Your Organization
31mHarmonizing Across Product & Engineering (Cross Team Collab)
23mExtreme Ownership for Global Teams
45mSW Design, Architecture & Clarity at Scale
27mDX for 10x IaC: The Force Awakens
26mCreating technical leadership in context
18mAgile leadership and technical mastery, a harmonious alliance