Skip to content

Review Committee aka Cheese Interface

Raimund Hook edited this page Mar 27, 2019 · 8 revisions

DEPRECATED

This pattern has been moved for discussion to
https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/43

Title

Review Committee (aka Cheese Interface)

Context

  • Company A wants to introduce its first InnerSource initiative.
  • Most managers in company A are not familiar with the Open Source working model.
  • Most managers in company A are accustomed to hierarchical, top-down control style management.

Problem

  • Managers either reject or micro manage the InnerSource initiative. As a result, the benefits of InnerSource can not be realized. InnerSource is discredited.

Forces

  • The more perceived control a manager has over the work in the inner source initiative, the more likely it is that he will support the initiative without prior experience.
  • The more heavy handed and micro managerial InnerSource initiatives are managed, the less likely it is that the open source working model can be adopted to the required extent. As a result, the benefits of InnerSource will not be realized.

Sketch (optional)

Solution

  • Establish a review committee to convene regularly (e. g. twice a year). The review committee has the authority to decide which InnerSource project is going to get approval and funding, based on data presented by the respective project.
  • Every InnerSource project is to be given the chance to react to feedback received on one session of the review committee until the next session in order to avoid shutting down the project prematurely.
  • An InnerSource project can also present the motion to be shut down on its own initiative on a review committee. The review committee then has to decide whether or not the business units using the software need to be given time to put measures in place to ensure that development and/or maintenance of the codebase continues until an alternative solution to development by the InnerSource community is found (if business relevant or mission critical).

Resulting Context

  • Managers get to apply a known tool in their toolbox to InnerSource in order to get the required amount of information about and control over the inner workings of the InnerSource initiative. This familiarity helps convince them to sign off on the initiative.
  • Developers can still self organise to a sufficient degree. Micro management does not happen because the review committee convenes rather infrequently.

Known instances

BIOS at Robert Bosch GmbH

Status

Draft Pattern

Authors

  • Georg Grütter, Robert Bosch GmbH
  • Diogo Fregonese, Robert Bosch GmbH
You can’t perform that action at this time.