Bringing Open-Source Brilliance to Scrum Teams: A Guide to Enhanced Collaboration

on YouTube ↗44m

" summary

Claim: applying open‑source practices inside companies (innerSource) raises transparency, developer experience and cross‑team reuse, backed by GitHub/GitLab workflows, Ruby gems examples and corporate programs. Evidence: community of over 3,000 individuals and 750 companies drives patterns like an inner source program office, trusted committer roles and a 30‑day warranty for contributions. Case signals: Bosch and PayPal reuse evidence, guidance focuses on making projects discoverable, composable, contributable and maintainable.

AI-written summary · about

" chapters (11)

1. 0:00Introduction and welcome
2. 1:48Why open source in Scrum?
3. 4:01What is inner source?
4. 8:42Inner source principles
5. 13:29Inner source vs reinventing the wheel
6. 16:24Key abilities of inner source projects
7. 20:29Starting an inner source program
8. 23:42Common misconceptions
9. 27:46Inner source as cultural transformation
10. 30:36Key takeaways and summary
11. 31:19Q&A session

" related talks

• 13mHow can we truly arrive at "open-source everywhere"?Danese Cooper · Collision 2017
• 30mInnersource: open source collaboration patterns beyond public FOSS projectsIsabel Drost-Fromm · GitHub Satellite 2019
• 54mInnerSource 101 and the Apache WayJim Jagielski · ApacheCon North America 2017
• 52mBottom-Up Open Source CultureRussell Rutledge · All Things Open 2020
• 15mAdopting Open Source Practices To Build More Inclusive Products and ServicesDavid Grizzanti · All Things Open 2021
• 26mWhy innersource is a critical component of FOSS sustainabilityDanese Cooper · GitHub Satellite Virtual 2020
• 19mHow to Become a Top-Performing Software Engineer through Open Source..Otavio Santana · GeeCON 2023
• 43mFostering an Open Source CultureArun Gupta · Open Source Leadership Summit @ Open Source Summit North America 2023