When there is no alternative to InnerSource
summary
Company moves from startup to post‑acquisition and finds InnerSource necessary to tame scale: engineering grows to 100+ engineers across 7 business domains supporting 250 mobile features and 3M MAU. InnerSource practices used are lightweight experiments, PRDs as cross‑team decision records, a single source of truth for docs, weekly cross‑stakeholder retros, and cross‑team project evaluation. Those practices reduce silos and analysis paralysis, improve scope tradeoffs against the Iron Triangle, and show measurable improvement while communication tooling and maturity still require work.
AI-written summary · about
chapters (9)
- 0:00Introduction and context
- 1:30What is InnerSource and why
- 4:23Scaling challenges in engineering
- 8:02Agile pitfalls during growth
- 11:40Siloed teams and visibility
- 13:24The Iron Triangle problem
- 15:57InnerSource practices at Instashop
- 17:26InnerSource patterns in action
- 18:10Q&A
related talks
28mBreaking Silos With InnerSource
47mWhat Is InnerSource? How Do You Implement It ...
16mEffective InnerSource Strategies for Resource-Constrained Teams
21mImplementing InnerSource as Culture for Sustainable Productivity & Innovation
14mAdopting InnerSource to maximize Developer Experience
12mIs the Future Forked? Navigating an Uncertain Era via InnerSource
14mBootstrapping InnerSource at Airbus
28mA Journey to Inner Source