OpennessIndex

Version 23.1 by Patrick Masson on 2017/06/24 22:48
Warning: For security reasons, the document is displayed in restricted mode as it is not the current version. There may be differences and errors due to this.

Objective

The term "open" has become popularly used to describe a variety of objects; software and technology, educational resources, education, etc. Ambiguity exists in the meaning of open. For example, open education, where anyone can enroll with only the requirement of a fee and no education, versus being available to anyone without cost. In addition to the ambiguity of open and what it enables, also lies ambiguity with the openness of  organizations.

The "Openness Index" attempts to define open attributes while assessing the type of openness within the community of practice who's responsible for the design, development, and distribution of the open artifact.

Importantly, the "Openness Index" is not designed to assess the openness of an artifact, object, software, OER, etc. claimed to be open. There are plenty of licenses that can be used to assess the openness of an object, rather an organization or community that creates and manages artifact.

Traditional Maturity Model Definition-

There are five levels defined along the continuum of a maturity model:
a. Initial (chaotic, ad hoc, individual heroics) - the starting point for use of a new   or undocumented repeat process.
b. Repeatable - the process is at least documented sufficiently such that repeating the same steps may be attempted.
C. Defined - the process is defined/confirmed as a standard business process, decomposed to levels 0, 1, and 2 (the latter being Work Instructions).
d. Managed - the process is quantitatively managed in accordance with agreed-upon metrics.
e. Optimized - process management includes deliberate process optimization/improvement.

"Opening" the Maturity Model Definition:

Using the above as a framework, the following can be applied to access the maturity of an open project:

  1. Initial/ Aware : (chaotic, ad hoc, individual heroics) - the starting point for use of a new or undocumented open project.
  2. Repeatable - openness is at least documented sufficiently such that repeating the same steps toward openness may be attempted.
  3. Defined - openness is defined/confirmed as a standard business process, and decomposed to levels 0, 1 and 2 (the latter being Work Instructions).
  4. Managed - openness is quantitatively managed in accordance with agreed-upon metrics (those of the OMM)
  5. Optimizing - openness management includes deliberate principle/process/practice optimization/improvement.

Openness Values

Courage

Courage is sufficient to participate in openness, however participants may be motivated by other causes, such as: a condition of employment; direction from a supervisor; peer pressure; or, a hidden agenda—perhaps to influence (or sabotage) direction.

Unknown macro: showhide. Click on this message for details.

Unknown macro: showhide. Click on this message for details.

Tags:
Created by Patrick Masson on 2014/12/15 20:34
    

Submit feedback regarding this wiki to webmaster@opensource.org

This wiki is licensed under a Creative Commons 2.0 license
XWiki 14.10.13 - Documentation