Upgrade to Pro — share decks privately, control downloads, hide ads and more …

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

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

Are you seeking transparency and good communication within your organization?
Do you want to improve the quality of collaboration both inside and outside of the Scrum team?

This session is for you. In this session, we will focus on how to effectively incorporate the methods and outstanding benefits of open-source collaboration into Scrum teams. We will introduce collaboration examples within GitHub and the approach of companies with excellent collaboration practices on GitHub. Through this, we will explore in detail how to roll out open-source fundamental principles, the pursuit of transparency, distribution of responsibility, and ways to enhance the quality of developer experience within the organization.

https://confengine.com/conferences/regional-scrum-gathering-tokyo-2024/schedule/rich#session-31489-info

Yuki Hattori

January 11, 2024
Tweet

More Decks by Yuki Hattori

Other Decks in Technology

Transcript

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

    View full-size slide

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

    View full-size slide

  3. Question:
    Does your organization have silos?

    View full-size slide

  4. Question:
    How open is your project or team?

    View full-size slide

  5. Question:
    How transparent is your project or team?

    View full-size slide

  6. Question:
    Do you want to collaborate like a community?

    View full-size slide

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

    View full-size slide

  8. What’s SCRUM?

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

  12. 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 full-size slide

  13. Why InnerSource at RSGT?

    View full-size slide

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

    View full-size slide

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

    View full-size slide

  16. Why InnerSource NOW?

    View full-size slide

  17. 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 full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

  23. 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 full-size slide

  24. 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 full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

  28. 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 full-size slide

  29. 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 full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

  39. 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!

    View full-size slide

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

    View full-size slide

  41. Customer Stories
    InnerSource with GitHub
    Appendix

    View full-size slide

  42. 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 full-size slide

  43. 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 full-size slide

  44. 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 full-size slide

  45. Having everyone together on the
    GitHub platform is a great advantage
    for InnerSource.

    Wolfgang Gehring / FOSS Ambassador
    Appendix / Customer Stories

    View full-size slide

  46. Resources
    InnerSource with GitHub
    Appendix

    View full-size slide

  47. Resources
    gh.io/innersource

    View full-size slide

  48. Resources
    gh.io/innersource/blog

    View full-size slide

  49. Resources
    innersourcecommons.org

    View full-size slide

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

    View full-size slide