Collaborative Waste: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 1: | Line 1: | ||
=Introduction= | |||
Collaborative waste is any ''waste'' that arises from large groups of people working together. There may be many sources of such waste: coordination losses, effort to produce documentation, etc. | |||
However, in the digital age, there are tools to manage effective collaboration between large groups: | |||
#Upvoting platforms | |||
=Article= | |||
*By [https://opensource.com/users/dbhurley] - 12 issues of open source - https://opensource.com/life/14/6/12-challenges-open-source-projects | *By [https://opensource.com/users/dbhurley] - 12 issues of open source - https://opensource.com/life/14/6/12-challenges-open-source-projects | ||
=Solutions= | ==Solutions== | ||
#Establishing a standard for code submissions | #Establishing a standard for code submissions | ||
| Line 8: | Line 18: | ||
##For HeroX - update videos for contributions. Rewarding your contributions. You MUST inform people of your work, and allow them to contribute | ##For HeroX - update videos for contributions. Rewarding your contributions. You MUST inform people of your work, and allow them to contribute | ||
==Scope Solutions== | ===Scope Solutions=== | ||
#Modular breakdown to as many small pieces as possible | #Modular breakdown to as many small pieces as possible | ||
#Doing critical contributions only, not derivative ones, and phasing progress. For ex, CAD is king as the deliverable; an exploded part diagram may be in a subsequent phase (User Manual Phase). | #Doing critical contributions only, not derivative ones, and phasing progress. For ex, CAD is king as the deliverable; an exploded part diagram may be in a subsequent phase (User Manual Phase). | ||
==Direction Solutions== | ===Direction Solutions=== | ||
#''Build it and show us the data'' puts a quick resulution of design debate | #''Build it and show us the data'' puts a quick resulution of design debate | ||
=Judging= | ==Judging== | ||
*Judging and peer review can be combined. You get rewarded for working on winning versions. This forces you to contribute to something that you deem worthy - which is a form of peer review. If you work on a dead end, sorry but no cigar. | *Judging and peer review can be combined. You get rewarded for working on winning versions. This forces you to contribute to something that you deem worthy - which is a form of peer review. If you work on a dead end, sorry but no cigar. | ||
[[Category:Incentive Challenge]] | [[Category:Incentive Challenge]] | ||
Revision as of 18:23, 22 August 2019
Introduction
Collaborative waste is any waste that arises from large groups of people working together. There may be many sources of such waste: coordination losses, effort to produce documentation, etc.
However, in the digital age, there are tools to manage effective collaboration between large groups:
- Upvoting platforms
Article
- By [1] - 12 issues of open source - https://opensource.com/life/14/6/12-challenges-open-source-projects
Solutions
- Establishing a standard for code submissions
- requiring acceptance of a common license
- implementing peer review are three ways in which good open source projects help to mitigate the risk of problematic code.
- For HeroX - update videos for contributions. Rewarding your contributions. You MUST inform people of your work, and allow them to contribute
Scope Solutions
- Modular breakdown to as many small pieces as possible
- Doing critical contributions only, not derivative ones, and phasing progress. For ex, CAD is king as the deliverable; an exploded part diagram may be in a subsequent phase (User Manual Phase).
Direction Solutions
- Build it and show us the data puts a quick resulution of design debate
Judging
- Judging and peer review can be combined. You get rewarded for working on winning versions. This forces you to contribute to something that you deem worthy - which is a form of peer review. If you work on a dead end, sorry but no cigar.