Adopting InnerSource to Maximize Developer Experience (DevEx)

Adopting InnerSource to Maximize Developer Experience (DevEx)
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.

Transcript

1. Yuki Hattori (@yuhattor)
   Customer Success Architect at GitHub
   Board Member at the InnerSource Commons Foundation Sept 10, 2023
   Adopting InnerSource
   to Maximize DevEx
   

   View Slide

2. Getting Started with
   InnerSource
   Why, How, What
   Appendix
   

   View Slide

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

   View Slide

4. 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.
   

   View Slide

5. Why InnerSource NOW? 🤔
   

   View Slide

6. 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
   

   View Slide

7. Consider a large company like Microsoft
   01-Jan-94
   01-Jan-95
   01-Jan-96
   01-Jan-97
   01-Jan-98
   01-Jan-99
   01-Jan-00
   01-Jan-01
   01-Jan-02
   01-Jan-03
   01-Jan-04
   01-Jan-05
   01-Jan-06
   01-Jan-07
   01-Jan-08
   01-Jan-09
   01-Jan-10
   01-Jan-11
   01-Jan-12
   01-Jan-13
   01-Jan-14
   01-Jan-15
   01-Jan-16
   01-Jan-17
   01-Jan-18
   01-Jan-19
   01-Jan-20
   01-Jan-21
   01-Jan-22
   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.
   

   View Slide

8. There is now a need to break down silos and
   accelerate innovation with a transparent
   culture like open source.
   

   View Slide

9. What do
   companies
   want?
   Talent attraction and retention
   Companies now need to
   place more emphasis on
   the Developer Experience.
   Productivity and cost savings
   Consistency and quality
   Security and compliance.
   Speed.
   * “Why your IT organization should prioritize developer experience” by
   McKinsey
   https://www.mckinsey.com/capabilities/mckinsey-digital/our-insights/tech-forward/why-your-it-organization-should-prioritize-developer-experience
   

   View Slide

10. 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.
    

    View Slide

11. 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
    

    View Slide

12. InnerSource connects teams and code
    on an enterprise-wide scale
    DevOps
    DevOps
    DevOps
    Waterfall
    DevOps
    Kanban
    

    View Slide

13. InnerSource Practices
    InnerSource with GitHub
    Appendix
    

    View Slide

14. 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
    

    View Slide

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

    View Slide

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

    View Slide

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

    View Slide

18. 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.
    

    View Slide

19. Customer Stories
    InnerSource with GitHub
    Appendix
    

    View Slide

20. 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
    

    View Slide

21. 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
    

    View Slide

22. 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
    

    View Slide

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

    View Slide

24. Resources
    GitHub Enterprise Platform
    Appendix
    

    View Slide

25. Resources
    gh.io/innersource
    

    View Slide

26. Resources
    gh.io/innersource/blog
    

    View Slide

27. Resources
    innersourcecommons.org
    

    View Slide

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

    View Slide

29. View Slide