Team Levels

Team Levels or Team Maturity is a metric that defines the maturity of a team, scored from 0-5, in so far as the metric leads to assessing the potential for rapid parallel development. This metric is useful to Process Managers - in so far as it helps the manager assess how much energy should be given to a certain team. For mature teams, it is OSE's interest to support these teams as much as possible - with supporting information or other ways that lead to the creation of Distributive Enterprise for creating the open source economy.

Project progress depends on the completeness of a team. Parallel development depends on the number of people available for development, their skill level, their collaborative literacy (understanding of collaboration and their willingness to engage in ego-less development), and processes/protocols to guide massive parallel development.

In the OSE Model, six or seven figure product development budgets are rendered obsolete, as an open, distributive enterprise protocol can both develop products and fund their development.

The Level 0 team contains a solo open source warrior, while Level 5 inluces a full team with leadership, SME-level expertise, and a membership with a clear team charter.

The following is a description of the elements defining a certain level of team maturity, taken from the perspective of distributed, autonomous development (ie, voluntary, unpaid development). The reference point is a zero-waste development process, with zero barriers to participation, resulting in Distributive Enterprise and the next trillion dollar economy, the open source economy.

Level 0

This is a solo developer who is producing design that they may be willing to share. However, since there is no declared license, and specifically no OSHWA-compliant license. This developer publishes some results, but without clear instructionals that would enable easy replication. This developer does not use the OSE Wiki or other platform with open source contributor terms. For the practical purpose of building upon such work, open source developers should attribute such work, use it, and contact the developer requesting further documentation, and clear license terms. Such due diligence is required to determine whether this person's work is usable at OSE. For all practical purposes, such a developer may have useful information, but the content may not be usable by OSE due to license incompatibility. In the latter case, such a developer is just about as good as if they did not exist, and for this reason, is called Level 0 and not considered as part of any OSE team.

Another Level 0 contributor - one not seen by OSE - is one who is working somewhere in the world, but without publishing, such that any broader audience is not aware of the work, and as such, cannot build upon it. Such knowledge is as if it did not exist from the OSE perspective, and is considered wasted human effort from the perspective of time-binding. This happens to be the case for many people coming in contact with OSE - individuals who say that they are working on great things, but as long as these things are not published - it is as good as if it didn't exist.