Large-Scale Collaborative Design: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 14: | Line 14: | ||
#'''Physical Plant and Hardware''' - dev kits, meetups, conspiring/development places, hackathons | #'''Physical Plant and Hardware''' - dev kits, meetups, conspiring/development places, hackathons | ||
#'''[[Stigmergic Design]]''' - Team Story Game for Collaborative Video protocol; seeded templates on the wiki. Wiki assets for a stygmergic, construction set appraoch. | #'''[[Stigmergic Design]]''' - Team Story Game for Collaborative Video protocol; seeded templates on the wiki. Wiki assets for a stygmergic, construction set appraoch. | ||
#'''Agility''' - Things change fast. A common trend for large development attempts is: (1) things explode in fruitful activity; (2) things collapse from all the activity. The solution is protocols and collaborative literacy of protocol-users. When documenting, always think of the next iteration, and how that will be documented, and how your documentation can be scaled readily to other projects, modules, and systems. Any development project should be [[Fractal]] - both self contained, but also a building block. | |||
=Links= | =Links= | ||
*[[Collaboration Architecture Log]] | *[[Collaboration Architecture Log]] | ||
Revision as of 20:01, 4 April 2020
Basic Coordination Requirements:
- Focus. If audacious goal is clear (such as getting past COVID), focus is still needed to develop products fully.
- Scalable platform - wiki is used in OSE's work. Social media, Jitsi Video Bridge, part libraries, FreeCAD, are all examples of scalable platforms.
- Collaborators - who is collaborating? Need a team based on massive transformative purpose, where 10x Is Easier Than 2x
- Documentation - most important asset. The OSE wiki is our repo.
- Development Process - standard product development, such as embodied in Development Template
- Task division - Kanban board, modular breakdown of Module Based Design, Collaboration Architecture
- Prototyping - Ideas are nothing without prototypes to validate them. There are many ways from 3DP, to calculations, to partial prototypes of Test-Driven Design. Doable via hackathons, startup camps, Incentive Challenges,. Extreme Manufacturing Workshops, Summers of Extreme Design-Build
- Review - SMEs and users feedback on the development
- Communication - video, social media, Slack, collaborative video protocol.
- Distillation - upvoting. Critical.
- Application - Developers must either engage in dogfooding or production/distribution to outside markets
- Physical Plant and Hardware - dev kits, meetups, conspiring/development places, hackathons
- Stigmergic Design - Team Story Game for Collaborative Video protocol; seeded templates on the wiki. Wiki assets for a stygmergic, construction set appraoch.
- Agility - Things change fast. A common trend for large development attempts is: (1) things explode in fruitful activity; (2) things collapse from all the activity. The solution is protocols and collaborative literacy of protocol-users. When documenting, always think of the next iteration, and how that will be documented, and how your documentation can be scaled readily to other projects, modules, and systems. Any development project should be Fractal - both self contained, but also a building block.