Slide 1

Slide 1 text

INNERSOURCE APPLYING OPEN SOURCE PRACTICES IN THE ENTERPRISE PAUL ADAMS 01-06-2018

Slide 2

Slide 2 text

2 Let’s Play A Game!

Slide 3

Slide 3 text

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)

Slide 4

Slide 4 text

Part I: What?

Slide 5

Slide 5 text

5 Let’s Talk About Zalando For A Moment

Slide 6

Slide 6 text

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

Slide 7

Slide 7 text

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

Slide 8

Slide 8 text

8 THE PILLARS OF RADICAL AGILITY

Slide 9

Slide 9 text

9 OK. So What About InnerSource?

Slide 10

Slide 10 text

10 “A Robust Approach To Team Collaboration.” - Andy Oram, PayPal SO… WHAT IS INNERSOURCE?

Slide 11

Slide 11 text

11 LESSONS TO BE LEARNED FROM OPEN SOURCE • Development without boundaries • Spiritually agile • Continuous * • Docs!

Slide 12

Slide 12 text

12 Time For Another Game!

Slide 13

Slide 13 text

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)

Slide 14

Slide 14 text

Part II: How?

Slide 15

Slide 15 text

15 Pull Requests: Am I Making A Mistake?

Slide 16

Slide 16 text

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)

Slide 17

Slide 17 text

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

Slide 18

Slide 18 text

18 THE “ERR… I GUESS I KNOW WHAT HAPPENED HERE” PR

Slide 19

Slide 19 text

19 THE “NOT TOO BAD AT ALL” PR

Slide 20

Slide 20 text

20 A PRIME EXAMPLE?

Slide 21

Slide 21 text

21 Let’s Talk: What Makes A PR A Good PR?

Slide 22

Slide 22 text

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.

Slide 23

Slide 23 text

Part III: Why?

Slide 24

Slide 24 text

24 Get Synchronized

Slide 25

Slide 25 text

PAUL ADAMS [email protected] opensource.zalando.com @therealpadams baggerspion.net 01-06-2018 OPEN SOURCE LEAD