Cross Section Between InnerSource & Agile: Improving the Impact of Technical Contributions Beyond Just Your Silo

Slide 1

Slide 1 text

IMPROVING THE IMPACT OF TECHNICAL CONTRIBUTIONS BEYOND JUST YOUR SILO CROSS SECTION BETWEEN INNERSOURCE & AGILE @_BILLYJF

Slide 2

Slide 2 text

CROSS SECTION BETWEEN INNERSOURCE & AGILE WHY OSCON? ▸ Improved engagement & gave my work purpose ▸ Rate of learning & exposure ▸ Skill development through contributions to diverse communities ▸ Work life balance through ongoing skill development ▸ Still in tech due to open source meet ups and conferences

Slide 3

Slide 3 text

OVERVIEW ▸ Sprint Safe Disengagement ▸ Leads to further engagement throughout the enterprise ▸ Enables additional InnerSource contributions ▸ Accelerate a unit’s velocity toward shared goals ▸ What is InnerSource? CROSS SECTION BETWEEN INNERSOURCE & AGILE

Slide 4

Slide 4 text

INCREMENTAL ARCHITECTURE

Slide 5

Slide 5 text

INCREMENTAL ARCHITECTURE STOP WRITING TECHNICAL STORIES

Slide 6

Slide 6 text

BUT, A LARGE PERCENTAGE OF OUR BACKLOG ARE ALL TECHNICAL STORIES ! Individual Contributor INCREMENTAL ARCHITECTURE

Slide 7

Slide 7 text

A NARRATIVE THAT TAKES A USER THROUGH SOME PROCESS THAT RESULTS IN A VALUABLE OUTCOME FOR THAT USER. @allenholub on User Stories INCREMENTAL ARCHITECTURE

Slide 8

Slide 8 text

TRY TO REPRESENT THE TECHNICAL REQUIREMENT AS TASKS WITHIN ONE OF THE FUNCTIONAL USER STORIES THAT IS RELIANT ON THIS TECHNICAL WORK Scrum Shortcuts Without Cutting Corners: Agile Tactics, Tools, & Tips INCREMENTAL ARCHITECTURE

Slide 9

Slide 9 text

WHY ROLL UP TECHNICAL TASKS INTO USER STORIES? ▸ Product Owner & Team ▸ Avoid tasks being ignored due to being “uninteresting to the customer” (Kniberg 2011) ▸ Appreciation for technical complexity inherent within stories INCREMENTAL ARCHITECTURE

Slide 10

Slide 10 text

WE HAVE TO DO TECHNICAL TASKS FOR OUR PROJECTS, BUT LET'S REPORT PROGRESS IN TERMS OF VALUE: DELIVERING WHAT CUSTOMERS WANT. http://bit.ly/2Ovy6JW INCREMENTAL ARCHITECTURE

Slide 11

Slide 11 text

“TECHNICAL STORIES” ARE THE TASKS THAT ROLL UP UNDER USER STORIES

Slide 12

Slide 12 text

YOUR CODE'S DESIGN MUST EVOLVE ALONG WITH YOUR UNDERSTANDING OF THE PRODUCT. https://holub.com/product/incremental-architecture/ INCREMENTAL ARCHITECTURE

Slide 13

Slide 13 text

INCREMENTAL ARCHITECTURE INVEST ▸ Independent ▸ Negotiable ▸ Valuable ▸ Estimate-able ▸ Small ▸ Testable

Slide 14

Slide 14 text

INCREMENTAL ARCHITECTURE WHY, WHAT, HOW, AND WHO? ▸ Why - Why is this story being proposed? ▸ What - What problem is it intending to resolve? ▸ How - How does this beneﬁt the business? ▸ Who - Who beneﬁts from it? What’s the impact? https://www.scrum.org/forum/scrum-forum/12317/technical-stories

Slide 15

Slide 15 text

WHAT OBSERVATIONS CAN WE MAKE FROM A USER STORY PERSPECTIVE? # Individual Contributor CROSS SECTION BETWEEN INNERSOURCE & AGILE

Slide 16

Slide 16 text

SPRINT SAFE DISENGAGEMENT

Slide 17

Slide 17 text

SPRINT SAFE DISENGAGEMENT SIGNALS TO INDIVIDUAL CONTRIBUTORS THAT THEY CAN REST EASY TONIGHT, AND INTO THE FUTURE.

Slide 18

Slide 18 text

SPRINT SAFE DISENGAGEMENT WHAT IS SPRINT SAFE DISENGAGEMENT? ▸ Revolves around ▸ What does the code review/deﬁnition of done require? ▸ What’s going to boomerang anyway while on call?

Slide 19

Slide 19 text

SPRINT SAFE DISENGAGEMENT ON TRACK USER STORIES: WHAT MIGHT A CODE REVIEW ENTAIL? ▸ What is the code coverage of the feature in development? ▸ Test coverage? ▸ Ops ▸ Logs, Metrics, Dashboards, and Alerts ▸ At 2:30 am, groggy and sleepy, how much effort will it take to restore service, or, answer questions about current operation of a feature in prod?

Slide 20

Slide 20 text

▸ What is the code coverage of the feature in development? ▸ Test coverage? ▸ Ops ▸ Logs, Metrics, Dashboards, and Alerts ▸ At 2:30 am, groggy and sleepy, how much effort will it take to restore service, or, answer questions about current operation of a feature in prod? PR NEEDS WORK ON TRACK USER STORIES: WHAT MIGHT A CODE REVIEW ENTAIL? SPRINT SAFE DISENGAGEMENT

Slide 21

Slide 21 text

REASONING ABOUT PROD ▸ Alerts ▸ Dashboards ▸ Logs ▸ Tests ▸ Page an off call engineer (worst case, hope for the best) ▸ Slack, Conﬂuence, … SPRINT SAFE DISENGAGEMENT

Slide 22

Slide 22 text

WHAT IS SPRINT SAFE DISENGAGEMENT GETTING ME? ▸ Code reviews are quick and in sprint ▸ Prod support kept to a minimum, less pages after hours ▸ Observability is maintained and improving as the code base evolves, per story or pull request ▸ Contributing with far higher levels of engagement across the organization, not just a given silo () SPRINT SAFE DISENGAGEMENT

Slide 23

Slide 23 text

WHAT IS INNERSOURCE?

Slide 24

Slide 24 text

No content

Slide 25

Slide 25 text

A WAY TO INCREASE COLLABORATION, CROSS TECH KNOWLEDGE, EASE BOTTLENECKS, AND ASSIST TEAMS IN GETTING NEEDED CHANGES IMPLEMENTED IN STACKS THEY DON’T OWN Checking Out InnerSource at PayPal CROSS SECTION BETWEEN INNERSOURCE & AGILE

Slide 26

Slide 26 text

ENGINEERS WERE ABLE TO FIND A NEW PURPOSE AND RENEW THE ENTHUSIASM THAT THEY MIGHT HAVE LOST OVER THE YEARS. Living in a BIOSphere at Robert Bosch CROSS SECTION BETWEEN INNERSOURCE & AGILE

Slide 27

Slide 27 text

No content

Slide 28

Slide 28 text

INNERSOURCE SUPPLEMENTATION

Slide 29

Slide 29 text

INNERSOURCE SUPPLEMENTATION WHY FAVOR INNERSOURCE? ▸ Momentum is often far greater and has wider focus ▸ Less engineering effort for your team/silo ▸ Less ongoing maintenance from team perspective ▸ Contributors have impact beyond their immediate team ▸ Active internal support inside the organization

Slide 30

Slide 30 text

INNERSOURCE PROVIDES ANOTHER LEVEL OF COLLABORATION BETWEEN UNITS BY SHARING BACKLOGS Connecting Teams with InnerSource at Erickson INNERSOURCE SUPPLEMENTATION

Slide 31

Slide 31 text

FAVOR PULL REQUESTS OVER FEATURE REQUESTS ▸ Additional velocity related to originating user stories ▸ Team needs enough bandwidth per sprint to allow for this ▸ Trusted Committer ▸ In other words ▸ Write access to a repo outside a contributor’s domain INNERSOURCE SUPPLEMENTATION

Slide 32

Slide 32 text

THE WORK SHOWN ON A PULL REQUEST WAS A CLEARER BASIS FOR DISCUSSION THAN INFORMAL REQUIREMENTS COMMUNICATED ACROSS UNIT BOUNDARIES Borrowing Open Source Practices at Europace INNERSOURCE SUPPLEMENTATION

Slide 33

Slide 33 text

THE BEST CONTRIBUTIONS ARE SMALL AND FREQUENT Connecting Teams with InnerSource at Erickson INNERSOURCE SUPPLEMENTATION

Slide 34

Slide 34 text

LEVERAGE INNERSOURCE ▸ Pull in what’s available ▸ Communities of practice (cop) ▸ Contribute or demo improvements in a related cop ▸ Enterprise aware INNERSOURCE SUPPLEMENTATION

Slide 35

Slide 35 text

PAY IT FORWARD ▸ Write a blog post ▸ Give a talk ▸ Share how the experience impacted your day to day work ▸ Tell your story, build others up INNERSOURCE SUPPLEMENTATION

Slide 36

Slide 36 text

TO GIVE ANYTHING LESS THAN YOUR BEST, IS TO SACRIFICE THE GIFT. Steve Prefontaine CROSS SECTION BETWEEN INNERSOURCE & AGILE

Slide 37

Slide 37 text

QUESTIONS? ▸ Incremental Architecture ▸ https://conferences.oreilly.com/oscon/oscon-or-2018/ public/schedule/detail/68250 ▸ http://www.innersourcecommons.org ▸ http://paypal.github.io/InnerSourceCommons/assets/ﬁles/ InnerSourceCommonsSurvey2016.pdf ▸ http://paypal.github.io/InnerSourceCommons/resources/ books/adoptinginnersource/ CROSS SECTION BETWEEN INNERSOURCE & AGILE