Skip to content

share-your-code-to-get-more-done.md

Latest commit

 

History

History
63 lines (41 loc) · 2.57 KB

share-your-code-to-get-more-done.md

File metadata and controls

63 lines (41 loc) · 2.57 KB

Title

Share Your Code to Get More Done

Patlet

Development teams working in silos cannot deliver software fast enough but have no obvious path to increase throughput, unaware that opening their codebase to InnerSource contributions could unlock capacity from developers across the organization. By building an evidence-based project plan showing the value of contributions and actively recruiting potential contributors, teams expand their effective development capacity without adding permanent headcount.

Problem

  • Developers do not realize that they can get more done by taking advantage of InnerSource
  • Developers continue to work in their silo or alone and never take the time invest in moving to InnerSource
  • Project Teams need a compelling reason to invest some time to make the change

Context

  • Development on a specific product is siloed and a finite number of developers are involved in development activity
  • Development progress is not moving fast enough
  • Developers are being asked to do more work than they can accomplish
  • Other developers are likely to work on the product if the opportunity to participate existed
  • Current developers are working near maximum efficiency

Forces

  • Developers have no extra time to shift to InnerSource
  • Management has not prioritized a shift to InnerSource
  • Adding staff to get the work done using traditional methods is not possible
  • The value of InnerSource is not included in the project plan

Sketch (optional)

Solution

  • Leverage existing case studies and collateral from InnerSource Commons to educate management on the value of investing in InnerSource.
  • Work with planning team to document an alternative project plan with some InnerSource activities and estimated benefits from realistic expected participation
  • Move the product code to an InnerSource compatible solution and open the code
  • Assign a portion of the developers time to work as reviewers to ensure inner sourcing activities are successful
  • Recruit potential contributors and inform them of the availability of the opportunity to participate
  • Align incentives to participation for both existing developers and contributors to encourage behavior

Resulting Context

  • Development previously done in a silo is on the InnerSource system
  • People from outside the traditional silo are contributing successfully
  • More development is getting done per period (sprint)

Known Instances

TBD

Status

  • Initial
  • Old status: Unproven
  • Old status: Idea

Author

David Marcucci

Alias

Old title: Share Your Code to Get More Done - Likely Contributors Variant