Implementing InnerSource as Culture for Sustainable Productivity & Innovation
summary
Gartner places inner source in the trough of disillusionment and surveys show only 33% of developers are satisfied with inner source support versus 75% satisfied with team collaboration and 42% with cross-team collaboration. The recommended route is practical: build platform engineering self‑service with reusable templates (example: vanilla JavaScript front‑end templates) and run community of practice forums; Verizon cuts marketing copy time from 15 to 2 days; use badges/leaderboards (PennyMay case) and measure reuse, delivery speed, quality, and retention.
AI-written summary · about
chapters (11)
- 0:00Introduction to InnerSource
- 1:56InnerSource in Gartner Hype Cycle
- 4:48Misconceptions about InnerSource
- 6:35InnerSource as a Culture
- 7:38Supporting InnerSource with Platform Engineering
- 10:52Platform Engineering in Action
- 12:35Community of Practice for InnerSource
- 15:03Sustaining InnerSource with Incentives
- 16:49Leadership Buy-in for InnerSource
- 18:35Key Recommendations for InnerSource
- 20:21InnerSource Beyond Open Source
related talks
23mAccelerate Innovation by Initiating InnerSourcing
19mWhen there is no alternative to InnerSource
14mAdopting InnerSource to maximize Developer Experience
17mEnhancing Developer Experience through InnerSource and Platform Engineering
19mApply InnerSource Patterns to drive Internal Developer Platform with Backstage
17mThe Agile and InnerSource playground
30mInnersource: open source collaboration patterns beyond public FOSS projects
14mCountercultural: InnerSource for Consultants