Collaborative Swarm Design: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
(Created page with "Collaborative design augmented to larger (swarm), real-time (as enabled by collaborative literacy), module-based design (scalable design process).")
 
No edit summary
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
Collaborative design augmented to larger (swarm), real-time (as enabled by collaborative literacy), module-based design (scalable design process).
Collaborative design augmented to larger (swarm), real-time (as enabled by collaborative literacy), module-based design (scalable design process). Basic method:
 
*Use [[vProcess]] library to design optimal process for the working group. This attains a work breakdown structure for the overall process.
*Once breakdown is achieved, all is documented in a Google Presentation, realtime, with as many pages started as team members. A 240 person team would involve 240 slides. For speed optimization, document may contain hyperlinked subdocuments to allow for access to working design in multiple documents instead of one - in case a single doc is too large.
*For each item - each person develops.
*Integration comes from vProcess map - in which shared understanding is attained by [[Time-Binding]] upon existing, standard processes
*Key is that each vProcess step is detailed granularly, such that we can pull up [[Design Guides]] at the product, module, part, and material level.
*This effectively taps multiple areas of expertise in diverse areas of endeavor.

Latest revision as of 00:26, 24 October 2024

Collaborative design augmented to larger (swarm), real-time (as enabled by collaborative literacy), module-based design (scalable design process). Basic method:

  • Use vProcess library to design optimal process for the working group. This attains a work breakdown structure for the overall process.
  • Once breakdown is achieved, all is documented in a Google Presentation, realtime, with as many pages started as team members. A 240 person team would involve 240 slides. For speed optimization, document may contain hyperlinked subdocuments to allow for access to working design in multiple documents instead of one - in case a single doc is too large.
  • For each item - each person develops.
  • Integration comes from vProcess map - in which shared understanding is attained by Time-Binding upon existing, standard processes
  • Key is that each vProcess step is detailed granularly, such that we can pull up Design Guides at the product, module, part, and material level.
  • This effectively taps multiple areas of expertise in diverse areas of endeavor.