Skip to content

Latest commit

 

History

History
73 lines (46 loc) · 2.69 KB

sustainable-innersource-program.md

File metadata and controls

73 lines (46 loc) · 2.69 KB
Raw

Title

Sustainable InnerSource Program

Patlet

I've started an InnerSource program - what next? How do I ensure InnerSource remains a part of how we create software in the long term?

Problem

Given an InnerSource program and/or community has been started within your organisation, you are unsure how to scale and/or sustain to ensure that InnerSource remains part of culture and best practice in the long term. When scaling and sustaining an InnerSource program fails, it leads to problems including unusable projects/products, an unengaged community, and loss of support from leadership.

Context

  • The problem exists in fledgling InnerSource programs/communities
  • You may not have full time support from an InnerSource or Open Source Program Office (ISPO/OSPO)
  • There is no clear vision on the future of the program
  • You are worried that key people will move on to new roles, momentum will be lost and silently die, or future leaders will stop supporting InnerSource.
  • You are an individual or organization who is concerned with the fragile state and future of highly-used and impactful InnerSource projects. (Sustain. 2017.)
  • There is increasing quantity and decreasing quality of InnerSource projects at your organization.

Forces

  • The business may not believe further investment in InnerSource is necessary
  • Key individuals may be seeking new challenges in other initiatives or job roles

Solutions

(Assumptions of possible solutions, as this is a donut Pattern)

  • Start an ISPO: strategy, resources, buy-in
  • Measure/prove value constantly
  • Training
  • InnerSource libraries that are critical to business success

Resulting Context

to-be-done

What is the situation after the problem has been solved? The original context is changed indirectly by way of the solution. Often this section can include discussion of the next possible Patterns/problems introduced. This section can be short in content - the solution may not introduce new problems or change much context.

Rationale (optional)

to-be-done

Explains why this is the right solution; using totally different words WHY this solution balances these forces and this context to solve this problem. Can expand on what-if's or theories.

Known Instances (optional)

to-be-done

Where has this been seen before? Helps to reinforce that this is a REAL pattern and that you match the context.

May mention:

  • A particular business
  • Anonymized instances ex: "3 companies have proven that this is a good solution" or "A large financial services org...".

Status

Initial (Donut)

Author(s)

Tom Sadler Chan Voong We welcome any authors who would like to contribute.