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

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

A developer's perspective on InnerSource and how it relates to agile in the enterprise while operating in an agile DevOps environment with many observations correlated to those outlined in "Adopting InnerSource - Principles and Case Studies" (http://paypal.github.io/InnerSourceCommons/resources/books/adoptinginnersource/).

Now streaming: https://youtu.be/7Ka_fJ1mgZw.

4813f9eeba90ce3bef852c9b7f3d0e8e?s=128

Billy Fisher

August 16, 2018
Tweet

Transcript

  1. IMPROVING THE IMPACT OF TECHNICAL CONTRIBUTIONS BEYOND JUST YOUR SILO

    CROSS SECTION BETWEEN INNERSOURCE & AGILE @_BILLYJF
  2. 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
  3. 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
  4. INCREMENTAL ARCHITECTURE

  5. INCREMENTAL ARCHITECTURE STOP WRITING TECHNICAL STORIES

  6. BUT, A LARGE PERCENTAGE OF OUR BACKLOG ARE ALL TECHNICAL

    STORIES ! Individual Contributor INCREMENTAL ARCHITECTURE
  7. A NARRATIVE THAT TAKES A USER THROUGH SOME PROCESS THAT

    RESULTS IN A VALUABLE OUTCOME FOR THAT USER. @allenholub on User Stories INCREMENTAL ARCHITECTURE
  8. 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
  9. 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
  10. 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
  11. “TECHNICAL STORIES” ARE THE TASKS THAT ROLL UP UNDER USER

    STORIES
  12. YOUR CODE'S DESIGN MUST EVOLVE ALONG WITH YOUR UNDERSTANDING OF

    THE PRODUCT. https://holub.com/product/incremental-architecture/ INCREMENTAL ARCHITECTURE
  13. INCREMENTAL ARCHITECTURE INVEST ▸ Independent ▸ Negotiable ▸ Valuable ▸

    Estimate-able ▸ Small ▸ Testable
  14. 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 benefit the business? ▸ Who - Who benefits from it? What’s the impact? https://www.scrum.org/forum/scrum-forum/12317/technical-stories
  15. WHAT OBSERVATIONS CAN WE MAKE FROM A USER STORY PERSPECTIVE?

    # Individual Contributor CROSS SECTION BETWEEN INNERSOURCE & AGILE
  16. SPRINT SAFE DISENGAGEMENT

  17. SPRINT SAFE DISENGAGEMENT SIGNALS TO INDIVIDUAL CONTRIBUTORS THAT THEY CAN

    REST EASY TONIGHT, AND INTO THE FUTURE.
  18. SPRINT SAFE DISENGAGEMENT WHAT IS SPRINT SAFE DISENGAGEMENT? ▸ Revolves

    around ▸ What does the code review/definition of done require? ▸ What’s going to boomerang anyway while on call?
  19. 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?
  20. ▸ 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
  21. REASONING ABOUT PROD ▸ Alerts ▸ Dashboards ▸ Logs ▸

    Tests ▸ Page an off call engineer (worst case, hope for the best) ▸ Slack, Confluence, … SPRINT SAFE DISENGAGEMENT
  22. 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
  23. WHAT IS INNERSOURCE?

  24. None
  25. 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
  26. 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
  27. None
  28. INNERSOURCE SUPPLEMENTATION

  29. 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
  30. INNERSOURCE PROVIDES ANOTHER LEVEL OF COLLABORATION BETWEEN UNITS BY SHARING

    BACKLOGS Connecting Teams with InnerSource at Erickson INNERSOURCE SUPPLEMENTATION
  31. 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
  32. 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
  33. THE BEST CONTRIBUTIONS ARE SMALL AND FREQUENT Connecting Teams with

    InnerSource at Erickson INNERSOURCE SUPPLEMENTATION
  34. LEVERAGE INNERSOURCE ▸ Pull in what’s available ▸ Communities of

    practice (cop) ▸ Contribute or demo improvements in a related cop ▸ Enterprise aware INNERSOURCE SUPPLEMENTATION
  35. 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
  36. TO GIVE ANYTHING LESS THAN YOUR BEST, IS TO SACRIFICE

    THE GIFT. Steve Prefontaine CROSS SECTION BETWEEN INNERSOURCE & AGILE
  37. 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/files/ InnerSourceCommonsSurvey2016.pdf ▸ http://paypal.github.io/InnerSourceCommons/resources/ books/adoptinginnersource/ CROSS SECTION BETWEEN INNERSOURCE & AGILE