The evaluation system
Published on April 29, 2011, edited by Tibi, Kurt, Ishan, Ian, Francois, and Steve. See original doc, last modified on Oct 14, 2012 before content was moved here. If you contribute to this doc make sure you respect Content rules.
Work on the value system is hosted on github. We are using REA (for Resources, Events and Agents) designed by Bill McCarthy of Michigan State University (See more on Bill McCarthy’s website). See a prototype HERE.
This system assists members in evaluating contributions. Contributions must be evaluated for every member, for every project.
The evaluation mechanism associates a quantity to the contribution. This quantity is about how much value has been created by a contribution. Qualities of contributions like earliness (related to the level of risk taken is investing early or later in a project), homogeneity (a measure of consistency of contributions over time), regularity (related to a stable pattern of contributions over time), commitment (a measure of the density of contributions over time), etc. act as modulators.
The evaluation of continuous contributions usually takes place at a later time after an activity has been recorded. Passion-driven activities, that are not directly related to a product or to a market, can be evaluated at a later time, once they are integrated into a project that has a defined path to the market.
The evaluation process is very context sensitive and subjective. The value of a contribution has many dimensions, see The value equation for continuous contributions.
[See discussions with Kurt, Bayle and Ishan in our mailing list about valuation.]