How Did Backstage Make 500+ Developers Happy in a Highly Regulated Enterprise
summary
Bankdata deploys Backstage as a single instance to standardize developer journeys across ~100 product teams and 500+ developers, building a developer portal plus an Automation Highway that scaffolds services via GitHub Actions and templates. A Mainframe approval plugin replaces a painful UI, and a simple post-run survey shows a 3.8 rating for the automation flow. Time-to-10-pull-request is chosen as a north-star metric but proving baselines and integrating regulated security controls slows delivery more than expected.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:01About Bank Data
- 3:42Why Backstage
- 6:22What did we do
- 17:22Baked Compliance
- 19:37Delivering Value
- 22:09Measuring Developer Experience
- 23:09Finding Your Way
- 25:10Questions
related talks
06mScaling Enterprise Platform Engineering with Backstage
39mUnlocking Backstage's potential: insights and solutions for a smoother developer experience
35mImproving Developer Experience with Backstage
29mHow We Made Backstage Improve Developer Efficiency of 1000+ En...
38mEnabling Developer Experience Journey in U.S. Bank
26mDivide & Collaborate: Creating Scalable and Healthy Backstage Ba...
23mOur Journey To a Unified Developer Experience With Backstage
06mHow to Succeed with Backstage