Bringing Open-Source Brilliance to Scrum Teams: A Guide to Enhanced Collaboration Yuki Hattori@yuhattor Board Member, The InnerSource Commons Foundation Customer Success Architect, GitHub

The InnerSource Commons Foundation InnerSource Commons is the world's largest community of InnerSource practitioners. It is dedicated to creating and sharing knowledge about InnerSource, the use of open source best practices for software development within the confines of an organization. Founded in 2015, the InnerSource Commons is now supporting and connecting around 3000 individuals from over 750 companies, academic institutions, and government agencies.

Question: Does your organization have silos?

Question: How open is your project or team?

Question: How transparent is your project or team?

Question: Do you want to collaborate like a community?

If you want to maximize your team's potential through an open, transparent, community- based way of working. This is the session for you

What’s SCRUM?

Visiting the definition of DevOps? https://www.linkedin.com/posts/patrickdebois_my-current-definition-of-devops-everything-activity-6755909565658746880-odKR/

Why not become a great scrum team that collaborates across silos?!

What is InnerSource? InnerSource is the application of open source principles to company-internal software development

It’s NOT just about doing open source practices InnerSource is a journey to culturally transform towards an internal sharing economy similar to open source, while respecting corporate culture and internal organizational constraints, and breaking down organizational silos.

Why InnerSource at RSGT?

InnerSource addresses the problem of scaling Scrum When you try to scale Scrum, • Collaboration teams do not always adopt Scrum • Lack of collaboration between Scrum teams The solution is NOT always to "get them to do Scrum too" or to ”make them to understand how our Scrum works.”

InnerSource connects teams and code on an enterprise-wide scale Scrum Scrum Scrum Waterfall Scrum Kanban

Why InnerSource NOW?

Why InnerSource NOW? Tim O'Reilly coined the term InnerSource in 2000, but it did not gain much traction at that time. But, what has happened since 2000? It's the prosperity of Open Source Software, the spread of the cloud, and software eating the world. Then, every company underwent a digital transformation to become a software company. 2000 2023 Evolution of Technology and Rapid Market Expansion

Consider a large company like Microsoft The number of employees went from 39,100 to 221,100. The number of products that grew also increased. A situation was born in which silos could easily be created.

Also AI is eating the world now Instead of competing only with function-specific single products, companies need to build an ecosystem that embeds their competitive advantage and compete not as a product but as a suite or company as whole

#InnerSource aka.ms/iscslack #jp-general Share the sources of competitiveness The “openness” of the project extends across many teams within the organization. This allows the organization to embed differentiating trade secrets into the code without fear that they will be revealed to outsiders, while benefitting from the creativity and diverse perspectives contributed by people throughout the organization. From “Getting Started with InnerSource” by Andy Oram, an editor for O'Reilly Media

There is now a need to break down silos and accelerate innovation with a transparent culture like open source in SCRUM TEAM!

#InnerSource aka.ms/iscslack #jp-general InnerSource in Action

InnerSource Principles Openness - Open projects must be sufficiently documented and discoverable by placing a README.md file and a CONTRIBUTING.md file at the top of the repository. Transparency - The direction of the project/repository, unresolved feature requirements, progress on feature requirements, and decisions of the host team are made transparent. Prioritized Mentorship - With prioritized mentorship from the host team to the guest team by Trusted Committers, contributors from the guest team are leveled up to fully understand and make changes to the host team's project/repository. Voluntary Code Contribution - Participation in InnerSource from both the guest team and host team is done based on their free will.

InnerSource is the core of the modern collaboration XP Collective Ownership DevOps Reduce organizational silos Team Topologies Collaboration across teams/ departments. InnerSource Platform Engineering Don't reinvent the wheel

InnerSource Benefit For Competitive Strategy: For DevEx • Innovation through co-creation • Synergy between products • Quality improvement • Cost reduction by preventing reinvention of the wheel • Transparent and collaborative culture • Skill improvement through sharing • Employee satisfaction

#InnerSource aka.ms/iscslack #jp-general How to start InnerSource Appendix

4 key abilities for InnerSource projects Discoverable Able for partner teams to search all codebases, documentation, and other relevant materials to explore the project without prior domain knowledge Composable Able to quickly and easily compile and execute the source code for the partner team, or easily use the source code as part of a separate project. Encapsulated and ready to execute. Contributable Able for partner teams to easily report issues, ask questions, suggest new features, and upstream commits in a positive manner without barriers Maintainable Able to keep the code maintained by a team that is capable of continuous upkeep

InnerSource Program Office - ISPO The InnerSource Program Office (ISPO) provides the means and environment to realize InnerSource within the organization. While the program office promotes development, it is not a development department or a gatekeeper. Main responsibility: • Sharing of InnerSource policies • Measuring InnerSource Metrics (eg. # of PR across teams) • Conducting mentoring/training • Developing incentive models • Ensuring appropriate tooling PR Cross Team PR % Q1 FY19 852k 37k 5.6% Q2 FY19 810k 35k 4.2% Q3 FY19 912K 39k 4.8% Q4 FY19 1.0M 46k 4.1% Q1 FY20 1.2M 43k 3.6% * The above is an example from Microsoft.

Best Practices - InnerSource Patterns Create a participatory system throughout the software lifecycle and publish design documents to facilitate early discussions. 30 Day Warranty Contracted Contributor InnerSource License Base Documentation InnerSource Portal Design Document Guiding Principles Trusted Committer Improve trust between the two teams by allowing contributors to fix bugs and suggest features with 30 days of support. Encourage contributions to InnerSource through formal contracts and agreements within the organization, rather than as volunteers. Provide a legal framework for sharing source code within an organization and offer new collaboration options. Index InnerSource project information to make it easier for contributors to discover projects of interest. Define ways to recognize ongoing contributor work. Provide standard project documentation and a self-service process for new contributors. Document and make widely available the key principles of InnerSource. Patterns Short Description

InnerSource Patterns https://patterns.innersourcecommons.org/

InnerSource Patterns https://patterns.innersourcecommons.org/

InnerSource Patterns https://patterns.innersourcecommons.org/

Common Misconceptions I'm using GitHub. I'm doing InnerSource, right? InnerSource means in-house production, right? InnerSource can be achieved by implementing tools

Common Misconception InnerSource means in-house production, right? InnerSource is a term coined by Tim O'Reilly in 2000 to describe the use of open source development methods* within a company. Perhaps someone you know is confusing the following terms with InnerSource. • Insourcing (as opposed to outsourcing) • In-house Production * “Inner-sourcing is the use of open source development techniques within the corporation.” by Tim O’Reilly in 2000

Common Misconception I'm using GitHub. I'm doing InnerSource, right? The idea that GitHub is all that’s needed to be InnerSource is a concept we fight against daily. Most people do not realize that it takes much more than GitHub to find, create, and grow open source communities. The communities create the software, not the other way around, but more often than not, large companies lack a sense of holistic community. From “Understanding the Innersource Checklist” by Silona Bonewald, the founding member of the InnerSource Commons.

Common Misconception InnerSource can be achieved by implementing tools How do we make better decisions and collaborate more, without spending more money? These are things that GitHub can not answer but InnerSource can. It is true that using a tool like GitHub to make version control easy, visible, and accessible is a step in the right direction. But we need to think beyond tools and their advantages and flaws, and consider people. From “Understanding the Innersource Checklist” by Silona Bonewald, the founding member of the InnerSource Commons.

Explanation of InnerSource by Golden Circle InnerSource is a journey to culturally transform towards an internal sharing economy similar to open source How: To foster a people-oriented culture, find sources of co-creation within the company, and nurture them as a community. What: Leverage open source development practices within your company Why: To enable good decision making and more collaboration at lower cost and eliminate friction between silos

InnerSource Unti-Patterns ISPO Policty Project Mindset Non-continuous projects No in-house developer Complex solution for a specific purpose Code end user is a non-developer Decide how people work Add new control processes Curate a code base Build new tools on your own Create new types of repositories You own your code Contribution is a "pastime" Reinventing the wheel Product = Code

Key Takeaways Let’s remove frictions between silos! Practice InnerSource to remove friction between silos! InnerSource is a corporate culture change journey Foster a people-oriented culture, find sources of open source within your company, and nurture them as a community!

#InnerSource aka.ms/iscslack #jp-general Apendix Appendix

Customer Stories InnerSource with GitHub Appendix

The InnerSource initiative thus became the key point. We made efforts to change the way of thinking and ideas by code sharing using GitHub “ Appendix / Customer Stories Tomohisa Handa / Manager, Agile Development

They can make suggestions and adopt a style of working that’s more open and fits their needs “ Appendix / Customer Stories Tom Erickson / Supervisor of Global Software Tools and Processes

3M uses GitHub to drive innersource initiatives, eliminate duplicative efforts, tap the organization’s collective knowledge, and collaborate across teams to improve software. “ Appendix / Customer Stories Paul Pottorff / Cloud and Security Architect

Having everyone together on the GitHub platform is a great advantage for InnerSource. “ Wolfgang Gehring / FOSS Ambassador Appendix / Customer Stories

Resources InnerSource with GitHub Appendix

Resources gh.io/innersource

Resources gh.io/innersource/blog

Resources innersourcecommons.org

Resources Recommended free book. innersourcecommons.org/learn/books/

No content