InnerSource: Applying Open Source Practices in the Enterprise

InnerSource: Applying Open Source Practices in the Enterprise

At some point you have to admit that your team has grown to the point it is no-longer a team. Perhaps it is a team of teams. At some point you might grow to the point that you're not a team of teams anymore either. You have grow to resemble a community and that is how you should work. InnerSource is the practice of taking the lessons that can be learned from Open Source and applying them to your internal software development processes.

In this session we will cover the fundamentals of InnerSource, with regards to team communication. You will learn about:

- Identifying when InnerSource becomes important and how to introduce the topic to your organisation;
- Understanding the concepts from Open Source development that are transferable to the enterprise;
- Tooling and Process;
- The importance of asynchronous communication.

The workshop will be combination of both presentation and games, so please come prepared to participate!

285e2691517b3ecd122e587c65e9d9ad?s=128

Paul Adams

June 01, 2018
Tweet

Transcript

  1. 3.

    3 WHAT DID YOU DO WITH THE 5th PLAYER? •

    Communication became asynchronous? • Communication became noisy? • Collaboration disappeared? • Did you even get the trash in the bin? • What if I’d asked you to do this blindfolded? “day 6” by TLA8 (https://flic.kr/p/x8P4k)
  2. 6.

    6 ZALANDO AT A GLANCE as at March 2018 ~

    4.5 billion EUR revenue 2017 > 200 million visits per month > 15,000 employees in Europe > 70% of visits via mobile devices > 23 million active customers > 300,000 product choices ~ 2,000 brands 15 countries
  3. 7.

    7 WE ARE CONSTANTLY INNOVATING TECHNOLOGY HOME-BREWED, CUTTING-EDGE & SCALABLE

    technology solutions ~ 2,000 employees from tech locations (HQs in Berlin) 7 77 nations help our brand to WIN ONLINE
  4. 11.

    11 LESSONS TO BE LEARNED FROM OPEN SOURCE • Development

    without boundaries • Spiritually agile • Continuous * • Docs!
  5. 13.

    13 WHO SAID “PULL REQUEST”? • README • End User

    Documentation • Website • Contributing • License • Issues • User Stories • Commit Messages • Code • Comments • ... “Tug of War” by toffehoff (https://flic.kr/p/nD2nk) “Tug of War” by toffehoff (https://flic.kr/p/nD2nk) “Tug of War” by toffehoff (https://flic.kr/p/nD2nk) “Tug of War” by toffehoff (https://flic.kr/p/nD2nk) “Tug of War” by toffehoff (https://flic.kr/p/nD2nk)
  6. 16.

    16 LOOK WHAT I DID! In GitHub’s own words: “Pull

    requests let you tell others about changes you've pushed to a GitHub repository.” - After the fact - “Let” is weak - “others”? “Acupuncture” by Petras Gagllas (https://flic.kr/p/iJoBE8)
  7. 17.

    17 HOW ABOUT THIS DESCRIPTION? “An asynchronous form of communication

    design to collect all communication related to the development of a specific feature.” - Paul Adams, Zalando
  8. 22.

    22 DID WE TALK ABOUT TIMING? “postits” by Peer 2

    Peer University (https://flic.kr/p/bt51RX) Ceremony Description Daily Scrum Probably no role here. Planning 1 Open PR. Planning 2 Complete the PR template. Review Merge the PR. Retro Perhaps process/template review. Backlog Refinement Probably no role here.