Collaborative Waste: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
However, in the digital age, there are tools to manage effective collaboration between large groups: | However, in the digital age, there are tools to manage effective collaboration between large groups: | ||
#Modular breakdown - breakdown of complex problems into small parts is a critical tool for solving large problems with many people | |||
#Role definition - defining clear roles, tasks, and skill sets required to work on tasks | |||
#Upvoting platforms for distilling content so content transforms from cacophony to distilled wisdom | #Upvoting platforms for distilling content so content transforms from cacophony to distilled wisdom | ||
#Wikis - to manage large amounts of data collaboratively | #Wikis - to manage large amounts of data collaboratively | ||
#Live editable documents - such as Google Presentation - for large realtime design effort | #Live editable documents - such as Google Presentation - for large realtime design effort | ||
# | #Part libraries and open source CAD - with clear submission and file format guidelines, large part libraries can be managed effectively for large scale collaboration where many people work on different modules | ||
Revision as of 18:25, 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:
- Modular breakdown - breakdown of complex problems into small parts is a critical tool for solving large problems with many people
- Role definition - defining clear roles, tasks, and skill sets required to work on tasks
- Upvoting platforms for distilling content so content transforms from cacophony to distilled wisdom
- Wikis - to manage large amounts of data collaboratively
- Live editable documents - such as Google Presentation - for large realtime design effort
- Part libraries and open source CAD - with clear submission and file format guidelines, large part libraries can be managed effectively for large scale collaboration where many people work on different modules
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.