Effective InnerSource Strategies for Resource-Constrained Teams
summary
Resource-limited teams convert constraints into a functioning InnerSource system by making projects discoverable, standardizing onboarding, and using existing infra rather than building new tools. A community of practice creates a backlog, runs mobbing sessions to produce an platform engineering handbook, and convinces the dev-intel team to version and extend the developer intelligence API so repositories can be queried by an inner source topic. Outcome: many projects now tagged, a searchable catalog, measurable growth in cross-team contributions and reuse.
AI-written summary · about
chapters (7)
- 0:00Introduction and journey
- 2:00Building inner source community
- 4:49Creating inner source recipe
- 7:39Patterns for resource-constrained teams
- 10:29Evangelism and group identity
- 14:23ISPO working group and metrics
- 15:50Summary and key components
related talks
19mWhen there is no alternative to InnerSource
14mAdopting InnerSource to maximize Developer Experience
30mInnersource: open source collaboration patterns beyond public FOSS projects
23mAccelerate Innovation by Initiating InnerSourcing
25mDriving the InnerSource Program at SAP
17mEnhancing Developer Experience through InnerSource and Platform Engineering
19mApply InnerSource Patterns to drive Internal Developer Platform with Backstage
17mThe Agile and InnerSource playground