Using experience-based acceleration to achieve your transformation
summary
Claims a repeatable method called Experience-Based Acceleration that runs three-day parties where cross-functional teams harden landing zones, migrate apps, and build automation; gives concrete results: SAP Concur removes 60+ blockers uncovered, deploys 19 apps to production during events and later migrates 700 microservices in three months; frames success patterns: executive sponsorship, aggressive top-down goals, start-before-plan, instrumented hands-on work and measurable organizational outcomes.
AI-written summary · about
chapters (16)
- 0:00Welcome and introduction
- 1:07Customer challenges in transformation
- 3:44SAP Concur case study
- 8:04What is EBA methodology
- 10:16Core types of EBA parties
- 12:50Amdocs case study
- 14:37Introduction to Scott Bends
- 17:30Success patterns under the hood
- 24:39Cross-functional team structure
- 28:15Two-way door decisions in cloud
- 30:21Cloud outcomes and deployment
- 33:18Organizational outcomes to track
- 37:13EBA as a discovered methodology
- 39:29Real-world EBA migration party
- 43:26Four-step acceleration process
- 49:30Final thoughts and next steps
related talks
32mSailing through Digital Transformation
39mAgility and SAP migration — the courage to dare, the discipline to succeed
26mAgile Transformations are not about software
48mAgility and Architecture Together – Enabling a Fast Flow of Change
54mGetting Unstuck. Strategies for Surviving in a Rapidly Changing Post-Agile World
42mCatastrophes and Atrophies
30mCase Study: EA in Serasa Experian's Agile Transformation
27mCrossing the transformation finish line