Please enable JavaScript.

Coggle requires JavaScript to display documents.

Adopting InnerSource Book, Danese Cooper, Klaas-Jan Stol - Coggle Diagram

- - - - meritocracy means that the more you do, the more merit you gain
    - - The code itself is transparent, in that it is visible to all.
      - the decision-making process itself, the discussions and conversations—all of this must be transparent.
      - letting contributors learn from others
    - - A shared culture that all members of that community understand and promote.
      - driving consensus
  - - - Linux Law
      - Contribution of experts
    - - Common group
      - Core Team
      - Trusted commiters
      - A growing community
  - - - Sponsorship for BIOS
      - Defined budget for communities
      - Corporate Research to the Corporate Engineering Department as a result.
    - - Transparency
      - Openness
      - Voluntariness
      - Self-determination
      - Meritocracy
        
        Based on the quality and quantity of contributions made.
    - - BIOS Review Committee
        
        VP, Engineering business units
        
        Community leaders to build community and inspire others
      - BIOS Governance Office (BGO)
        
        1.5 million euro budget to manage BIOS
        
        Reimburse engineer's time % in money to the business unit
    - - 2018, crowdfunding campaing. budget from business units
      - 2019, Decentralized community of Social coding avocades
    - - Improved collaboration
      - Personal growth
      - Increased productivity
      - Alignment with business
      - Highly motivated people = More volunteers
    - - Attract people when they are dedicated to a specific business unit
      - Getting buy-in and commitment from management
      - HR was not involved to rewards the time spend voluntary
      - Think about marketing, to promote the BIOS
  - - - Pull requests instead of feature requests
      - Trusted Committers who review submitted code
      - Suitable extrinsic rewards to overcome reticence
      - Written communication that is archived and searchable
    - - Checkout experiment
        
        Identify 10% of engineers to become in a Trusted Commiter
        
        Anti-pattern: Only engineer to engineer approach
        
        Product Management Owner were out
      - Onboarding experiment
        
        Bootcamp: 75 engineers, 2 weeks,
        build relationships and know about codebase.
        
        Anti-pattern: Content delivery verbally and not documented.
        
        Cost pretty high for these training sessions
      - Executive Air cover, Symphony project
        
        December 2015, meeting with.
        Senior managers, Product Owners, InnerSource Team.
        
        Added CONTRIBUTING.md file
    - - Guest adding contributions, host changing the original contributions.
      - Fear of increased workload, of being conscripted
      - Fear of insufficient ability with written English
      - Fear of accepting gift code and then having the burden to maintain it.
      - Changing staff
      - Difficulty scheduling meetings for team in different geography locations
    - - Introduction to InnerSource
        Fundations for InnerSource
      - The role of the contributor,
        How to be a good guest, give support after contributing and accept critique.
      - Trusted commitership
        How to be a good host, and mentor to contributors
      - InnerSource for Product Managers
        How to negotiate with PMO and schedule work.
      - Each training includes, resources, and Q&A, quizzes to prove the understanding.
    - - InnerSource stories completed per sprint
    - - Since 2017,
        to adopt InnerSource across all Paypal
      - Scaling InnerSource takes planning and time.
      - Re-training teams
  - - - Finding a better balance of autonomy and collaboration
      - Improving task transparency
      - Evolving teams and accountability. Trusted commiter
      - Building Trust in Written Communication
      - Scaling InnerSource Beyond First Experiments
      - Getting Other, Nondeveloper Colleagues on Board
      - Active contributors instead of passive consumers
    - - Meritocracy, Trusted comiter
      - Identify groups of stakeholders for InnerSource and getting people onboarded
      - Leading by example
    - - Make everything open, transparent, and findable
      - Encourage contributions over feature requests
      - Favor written over verbal communication
      - Embrace mistakes
      - Welcome all contributions
      - Maintain a project memory
  - - - Reducing waste of time and energy
      - Improving quality in software
      - Engineers were skeptical about this model at the beginning.
      - Convince to Product Owner and engineers about this cultural mindset.
    - - Starting the Community Developed Software Program
      - Creating Core Teams
        
        Product Owner
        
        Architect
        
        Code Guardian
      - Setting up contribution rules
      - Governance council, technical members
      - Marketplace: One-stop shop, components used by teams
        low-hanging fruit, common components.
      - Overlaying the different roadmaps. Product Owners and Architects
      - Collaboration workflow
        
        Discover
        
        Discuss
        
        Issues: JIRA
        
        Clone and implement
        
        Submit: PR, Code Review
        
        CI / Release
    - - Community portal: Marketplace, checklist, documentation.
      - Skilled people: Product Owners, Engineers, Architects
      - Best-in-class SDKs, libraries
      - Responsive Agile: Demos, backlogs, burndown charts, bug trackers
      - Active community: Mailing list, channels, hackathons, workshops
  - - - Transparency
      - Meritocracy
      - Respect
      - Open Minded
    - - Active contributors vs passive consumers
    - - Marketplace
      - Demo Days
      - InnerSource AMA / Q&A
- - - - Removes a bottleneck
      - Has development potential
      - Has different stakeholders
      - Has sufficiently modular structure, or seeks to become more modular
  - - - Simplicity
      - Facilitate synchronized schedules
      - Put quality assurance in place
      - Deploy compatible code management tools
  - - - Identify champions
      - Establish new roles
      - Prevent brand dilution
    - - Open up everything
      - Establish house rules
      - Market your program
    - - Executive management commitment
      - Staying in the radar
      - Strategic humility
      - :star: Address Fear, Uncertainty, and Doubt