Incentive Challenge Reward Structure: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(→Reward) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
=Reward= | |||
This is $100k for a large-scale, high T printer. | This is $100k for a large-scale, high T printer. | ||
#Grand Prize - $25k. For a | #Grand Prize - $25k. For a winner that produces a working printer that meets design specs and demonstrates a successful print. If the specifications are not met - prize is not awarded at all. Contest deadline is extended and any rules are modified as needed. | ||
#Second - 10x $5k | #Second - 10x $5k | ||
#Third - | #Third - 20x $1k | ||
#Contributor - 20x $250. | |||
#Crowdfunded - more $1k prizes. | #Crowdfunded - more $1k prizes. | ||
| Line 11: | Line 13: | ||
#Design must include an open enterprise blueprint for production, including data on production rates, feedstocks, parameters, etc. | #Design must include an open enterprise blueprint for production, including data on production rates, feedstocks, parameters, etc. | ||
#Must use OSE Linux to develop so everyone is coordinated. | #Must use OSE Linux to develop so everyone is coordinated. | ||
=Incentives= | |||
#'''Collaboration''' - Prize requires that the task is achieved: if the 4x8' printing printer is not produced AND documented - the reward is not awarded. This forces people to collaborate - as the 6 month deadline is too short for anyone to do it on their own. | |||
#'''Encourage Collaboration''' - it is in the interest of the development leaders to publish and be transparent - as qaulity documentation is a requirement. | |||
#'''The Team is every participant, and not exclusive teams.''' There is no subgroup to keep information hidden - points are scored by publishing, collaborating, and educating. | |||
#'''Changing the World with Enterprise''' - to make this spread, enterprise documentation is required as part of success. | |||
#'''Both MVP Burndown and Optimization is Rewarded''' - specifications define a minimum, and also an optimum state. The minimum state is required for reward to happen. Small prizes are awarded for the improvements. No disbursement occurs without MVP - so optimization workers are encouraged to work on MVP first. | |||
#'''Judging panel is objective''' - Clear specifications are defined for how 100% of the points are scored. This focuses developer effort. | |||
#'''Score is cumulative''' - this encourages people to participate to the end. | |||
#'''Effort is Expansive''' - additional reward money is collected throughout. This encourages wider collaboration. | |||
Latest revision as of 23:51, 29 August 2020
Reward
This is $100k for a large-scale, high T printer.
- Grand Prize - $25k. For a winner that produces a working printer that meets design specs and demonstrates a successful print. If the specifications are not met - prize is not awarded at all. Contest deadline is extended and any rules are modified as needed.
- Second - 10x $5k
- Third - 20x $1k
- Contributor - 20x $250.
- Crowdfunded - more $1k prizes.
Enterprise model - blueprint must be developed as an Enterprise Manual and a fully-functional plastic plant with high T printer, and filament maker.
- Must include a few excellent designs, such as chair, desk, a wikihouse, trim and more.
- Design must include an open enterprise blueprint for production, including data on production rates, feedstocks, parameters, etc.
- Must use OSE Linux to develop so everyone is coordinated.
Incentives
- Collaboration - Prize requires that the task is achieved: if the 4x8' printing printer is not produced AND documented - the reward is not awarded. This forces people to collaborate - as the 6 month deadline is too short for anyone to do it on their own.
- Encourage Collaboration - it is in the interest of the development leaders to publish and be transparent - as qaulity documentation is a requirement.
- The Team is every participant, and not exclusive teams. There is no subgroup to keep information hidden - points are scored by publishing, collaborating, and educating.
- Changing the World with Enterprise - to make this spread, enterprise documentation is required as part of success.
- Both MVP Burndown and Optimization is Rewarded - specifications define a minimum, and also an optimum state. The minimum state is required for reward to happen. Small prizes are awarded for the improvements. No disbursement occurs without MVP - so optimization workers are encouraged to work on MVP first.
- Judging panel is objective - Clear specifications are defined for how 100% of the points are scored. This focuses developer effort.
- Score is cumulative - this encourages people to participate to the end.
- Effort is Expansive - additional reward money is collected throughout. This encourages wider collaboration.