How to Adopt Backstage: Lessons from 20 Adopter Interviews
summary
Twenty interviews with adopters from ~80 to 2,000+ engineers surface concrete takeaways: 12 of 20 rely on catalog-info.yaml files, but only two teams reach high catalog completeness and many stall around ~25%; scaffolder succeeds for every team that actually tries it while nine teams never try it; TechDocs adoption splits roughly 6/6/6/2 (succeed/fail/too early/unknown); 7 teams using custom processors all succeeded; about half build maturity metrics into Backstage.
AI-written summary · about
chapters (11)
- 0:00Backstage adoption intro
- 1:03Research methodology
- 3:55Quantitative findings
- 7:25Scaffolder templates key
- 10:59Catalog population tips
- 14:55Automating catalog collection
- 16:38TechDocs adoption factors
- 18:27Plugin selection strategies
- 20:40Software maturity metrics
- 22:26Two paths to success
- 24:30Q&A
related talks
31mBackstage Adoption Deep Dive - Navigating the Pitfalls
36m4 Common Pitfalls when Adopting Backstage
27mLessons from a Year with Backstage: What Worked, What Didn’t...
32mIs Backstage for me?
22mUnlocking Backstage’s Potential: Driving Adoption and Maturity With Your Develope...
13mKeynote: 4 Common Pitfalls to Avoid When Onboarding Backstage
06mHow to Succeed with Backstage
29mAutomatically generate Backstage entity descriptors for easy adoption