Large-Scale Collaborative Design - Revision history

Marcin: /* Introduction */

2020-10-18T23:40:39Z

Introduction

← Older revision		Revision as of 23:40, 18 October 2020
Line 3:		Line 3:
	For large scale collaborative development to occur, there are 3 scales of operation for contributors. This applies to any collaborative design, whether CAD, graphics assets generation, video production, documentation, or enterprise creation etc.		For large scale collaborative development to occur, there are 3 scales of operation for contributors. This applies to any collaborative design, whether CAD, graphics assets generation, video production, documentation, or enterprise creation etc.

	The 3 scales or ~~Levelsare~~:		The 3 scales or Levels are:

	#'''Generation of atomic assets''' - such as a single part in CAD, an image, an icon, software module, electronic diagram, a diagram, a video clip, etc.		#'''Generation of atomic assets''' - such as a single part in CAD, an image, an icon, software module, electronic diagram, a diagram, a video clip, etc.

Marcin at 22:07, 18 October 2020

2020-10-18T22:07:55Z

← Older revision		Revision as of 22:07, 18 October 2020
Line 3:		Line 3:
	For large scale collaborative development to occur, there are 3 scales of operation for contributors. This applies to any collaborative design, whether CAD, graphics assets generation, video production, documentation, or enterprise creation etc.		For large scale collaborative development to occur, there are 3 scales of operation for contributors. This applies to any collaborative design, whether CAD, graphics assets generation, video production, documentation, or enterprise creation etc.

	The 3 scales ~~are~~:		The 3 scales or Levelsare:

	#'''Generation of atomic assets''' - such as a single part in CAD, an image, an icon, software module, electronic diagram, a diagram, a video clip, etc.		#'''Generation of atomic assets''' - such as a single part in CAD, an image, an icon, software module, electronic diagram, a diagram, a video clip, etc.
Line 11:		Line 11:
	At each level, the base atomic unit of development must be defined. Ie, what constitutes an 'atomic unit'? An 'assembly'? An Extreme Enterprise?		At each level, the base atomic unit of development must be defined. Ie, what constitutes an 'atomic unit'? An 'assembly'? An Extreme Enterprise?

	In ~~Step~~ 1, individuals work on a specific part. Multiple individuals can work on atomic units by mainatining work logs, and reconciling design merges as late in the process as possible according to the [[Second Toyota Paradox]]. There is no locking of design as in typical design processes, because the effort is an open process with open boundaries for unlimited collaboration potential. The prerequisite knowledge for Step 1 is as small as basic proficiency in the atomic tool of choice (FreeCAD, Blender, Inkscape, SweetHome3d, etc). Such proficiency can be attained in 1 hour using a common software platform such as [[OSE Linux]] combined with effective rapid-learning materials for that tool. This should allow a complete novice to join the process and make meaningful contributions within one hour of onboarding time.		==Level 1==
			In Level 1, individuals work on a specific part. Multiple individuals can work on atomic units by mainatining work logs, and reconciling design merges as late in the process as possible according to the [[Second Toyota Paradox]]. There is no locking of design as in typical design processes, because the effort is an open process with open boundaries for unlimited collaboration potential. The prerequisite knowledge for Step 1 is as small as basic proficiency in the atomic tool of choice (FreeCAD, Blender, Inkscape, SweetHome3d, etc). Such proficiency can be attained in 1 hour using a common software platform such as [[OSE Linux]] combined with effective rapid-learning materials for that tool. This should allow a complete novice to join the process and make meaningful contributions within one hour of onboarding time.

	In ~~step~~ 2, coordination of moudules and interfaces is performed, based on preliminary interface design which defines how parts fit together. For this to be done effectively, collaborators need to understand the modular breakdown of the product of interest, so that they can make the assemblies according to design rules. Design rules should be captured in a Design Guilde. Just like in Step 1, [[Test-Driven Design]] should be used, and reconciliation of design merges should be performed as late in the process as possible just like in Step 1.		==Level 2==
			In Level 2, coordination of moudules and interfaces is performed, based on preliminary interface design which defines how parts fit together. For this to be done effectively, collaborators need to understand the modular breakdown of the product of interest, so that they can make the assemblies according to design rules. Design rules should be captured in a Design Guilde. Just like in Step 1, [[Test-Driven Design]] should be used, and reconciliation of design merges should be performed as late in the process as possible just like in Step 1.

	~~Step~~ 3 requires more process design and business process design understanding so that business processes can be developed towards viable enterprises. Product managers at the Step 3 level should leverage [[Extreme Enterprise]] strategies including incentive challenges, backed by hands-on build events, enterprise opportunities, and product acquisition strategies for stakeholders with direct interest in the product. The direct stakeholders thus fund the product development, under the assumption that an important product is being developed.		The crash training required for Level 2 collaboration should be around one hour, to coordinate people around concepts of [[Wikis]], [[Realtime Cloud Collaborative Editing]], [[Work Logs]], [[Part Libraries]], and [[Version Control]].

			==Level 3==
			Level 3 requires more process design and business process design understanding so that business processes can be developed towards viable enterprises. Product managers at the Step 3 level should leverage [[Extreme Enterprise]] strategies including incentive challenges, backed by hands-on build events, enterprise opportunities, and product acquisition strategies for stakeholders with direct interest in the product. The direct stakeholders thus fund the product development, under the assumption that an important product is being developed.

	=Basic Coordination Requirements=		=Basic Coordination Requirements=

Marcin: /* Introduction */

2020-10-18T22:04:43Z

Introduction

← Older revision		Revision as of 22:04, 18 October 2020
Line 1:		Line 1:
	=Introduction=		=Introduction=

	For large scale collaborative development to occur, there are 3 scales of operation for contributors. This applies to any collaborative design, whether CAD, graphics assets generation, video production, documentation, etc.		For large scale collaborative development to occur, there are 3 scales of operation for contributors. This applies to any collaborative design, whether CAD, graphics assets generation, video production, documentation, or enterprise creation etc.

	The 3 scales are:		The 3 scales are:

Marcin at 22:04, 18 October 2020

2020-10-18T22:04:11Z

← Older revision		Revision as of 22:04, 18 October 2020
Line 13:		Line 13:
	In Step 1, individuals work on a specific part. Multiple individuals can work on atomic units by mainatining work logs, and reconciling design merges as late in the process as possible according to the [[Second Toyota Paradox]]. There is no locking of design as in typical design processes, because the effort is an open process with open boundaries for unlimited collaboration potential. The prerequisite knowledge for Step 1 is as small as basic proficiency in the atomic tool of choice (FreeCAD, Blender, Inkscape, SweetHome3d, etc). Such proficiency can be attained in 1 hour using a common software platform such as [[OSE Linux]] combined with effective rapid-learning materials for that tool. This should allow a complete novice to join the process and make meaningful contributions within one hour of onboarding time.		In Step 1, individuals work on a specific part. Multiple individuals can work on atomic units by mainatining work logs, and reconciling design merges as late in the process as possible according to the [[Second Toyota Paradox]]. There is no locking of design as in typical design processes, because the effort is an open process with open boundaries for unlimited collaboration potential. The prerequisite knowledge for Step 1 is as small as basic proficiency in the atomic tool of choice (FreeCAD, Blender, Inkscape, SweetHome3d, etc). Such proficiency can be attained in 1 hour using a common software platform such as [[OSE Linux]] combined with effective rapid-learning materials for that tool. This should allow a complete novice to join the process and make meaningful contributions within one hour of onboarding time.

	In step 2, coordination of moudules and interfaces is performed, based on preliminary interface design which defines how parts fit together.		In step 2, coordination of moudules and interfaces is performed, based on preliminary interface design which defines how parts fit together. For this to be done effectively, collaborators need to understand the modular breakdown of the product of interest, so that they can make the assemblies according to design rules. Design rules should be captured in a Design Guilde. Just like in Step 1, [[Test-Driven Design]] should be used, and reconciliation of design merges should be performed as late in the process as possible just like in Step 1.

	~~Basic units are synthesized~~ in ~~Step2~~		Step 3 requires more process design and business process design understanding so that business processes can be developed towards viable enterprises. Product managers at the Step 3 level should leverage [[Extreme Enterprise]] strategies including incentive challenges, backed by hands-on build events, enterprise opportunities, and product acquisition strategies for stakeholders with direct interest in the product. The direct stakeholders thus fund the product development, under the assumption that an important product is being developed.

	=Basic Coordination Requirements=		=Basic Coordination Requirements=

Marcin: /* Introduction */

2020-10-18T21:57:17Z

Introduction

← Older revision		Revision as of 21:57, 18 October 2020
Line 9:		Line 9:
	#'''Global Collaborative Process''' - coordinating the entire process towards creation of [[Extreme Enterprise]] and thus [[Distributed Market Substitution]].		#'''Global Collaborative Process''' - coordinating the entire process towards creation of [[Extreme Enterprise]] and thus [[Distributed Market Substitution]].

	At each level, the base atomic unit of development must be defined.		At each level, the base atomic unit of development must be defined. Ie, what constitutes an 'atomic unit'? An 'assembly'? An Extreme Enterprise?

	In Step 1, individuals work on a specific part. ~~Elements~~ of Step 2 and ~~3 can~~		In Step 1, individuals work on a specific part. Multiple individuals can work on atomic units by mainatining work logs, and reconciling design merges as late in the process as possible according to the [[Second Toyota Paradox]]. There is no locking of design as in typical design processes, because the effort is an open process with open boundaries for unlimited collaboration potential. The prerequisite knowledge for Step 1 is as small as basic proficiency in the atomic tool of choice (FreeCAD, Blender, Inkscape, SweetHome3d, etc). Such proficiency can be attained in 1 hour using a common software platform such as [[OSE Linux]] combined with effective rapid-learning materials for that tool. This should allow a complete novice to join the process and make meaningful contributions within one hour of onboarding time.

			In step 2, coordination of moudules and interfaces is performed, based on preliminary interface design which defines how parts fit together.

	Basic units are synthesized in Step2		Basic units are synthesized in Step2

Marcin: /* Introduction */

2020-10-18T21:50:28Z

Introduction

← Older revision		Revision as of 21:50, 18 October 2020
Line 7:		Line 7:
	#'''Generation of atomic assets''' - such as a single part in CAD, an image, an icon, software module, electronic diagram, a diagram, a video clip, etc.		#'''Generation of atomic assets''' - such as a single part in CAD, an image, an icon, software module, electronic diagram, a diagram, a video clip, etc.
	#'''Assemblies or Compositions''' - such as an entire product in CAD, a movie, a product brochure, uor any finished product.		#'''Assemblies or Compositions''' - such as an entire product in CAD, a movie, a product brochure, uor any finished product.
	#'''Global Collaborative Process''' - coordinating the		#'''Global Collaborative Process''' - coordinating the entire process towards creation of [[Extreme Enterprise]] and thus [[Distributed Market Substitution]].

	At each level, the base atomic unit of development must be defined.		At each level, the base atomic unit of development must be defined.

Marcin: /* Introduction */

2020-10-18T21:49:40Z

Introduction

← Older revision		Revision as of 21:49, 18 October 2020
Line 1:		Line 1:
	=Introduction=		=Introduction=

	For large scale collaborative development to occur, there are 3 scales of operation for contributors. This applies to any collaborative design, whether CAD, graphics assets generation, video production, documentation, etc. [[		For large scale collaborative development to occur, there are 3 scales of operation for contributors. This applies to any collaborative design, whether CAD, graphics assets generation, video production, documentation, etc.

	The 3 scales,		The 3 scales are:

			#'''Generation of atomic assets''' - such as a single part in CAD, an image, an icon, software module, electronic diagram, a diagram, a video clip, etc.
			#'''Assemblies or Compositions''' - such as an entire product in CAD, a movie, a product brochure, uor any finished product.
			#'''Global Collaborative Process''' - coordinating the

	At each level, the base atomic unit of development must be defined.		At each level, the base atomic unit of development must be defined.

			In Step 1, individuals work on a specific part. Elements of Step 2 and 3 can

			Basic units are synthesized in Step2

	=Basic Coordination Requirements=		=Basic Coordination Requirements=

Marcin at 21:26, 18 October 2020

2020-10-18T21:26:02Z

← Older revision		Revision as of 21:26, 18 October 2020
Line 1:		Line 1:
	=Introduction=		=Introduction=

	For large scale collaborative development to occur, there are 3 scales of operation for contributors. This applies to any collaborative design, whether CAD, graphics assets generation, video production, documentation, etc. At each level, the base atomic unit of development must be ~~defines~~.		For large scale collaborative development to occur, there are 3 scales of operation for contributors. This applies to any collaborative design, whether CAD, graphics assets generation, video production, documentation, etc. [[

			The 3 scales,


			At each level, the base atomic unit of development must be defined.

	=Basic Coordination Requirements=		=Basic Coordination Requirements=

Marcin at 21:11, 18 October 2020

2020-10-18T21:11:01Z

← Older revision		Revision as of 21:11, 18 October 2020
Line 1:		Line 1:
	=		=Introduction=

			For large scale collaborative development to occur, there are 3 scales of operation for contributors. This applies to any collaborative design, whether CAD, graphics assets generation, video production, documentation, etc. At each level, the base atomic unit of development must be defines.

	=Basic Coordination Requirements=		=Basic Coordination Requirements=

Marcin at 21:07, 18 October 2020

2020-10-18T21:07:09Z

← Older revision		Revision as of 21:07, 18 October 2020
Line 5:		Line 5:
	#'''Focus'''. If audacious goal is clear (such as getting past COVID), focus is still needed to develop products fully.		#'''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. Scalability key is simplicity and rapid onboarding.		#'''Scalable platform''' - wiki is used in OSE's work. Social media, Jitsi Video Bridge, part libraries, FreeCAD, are all examples of scalable platforms. Scalability key is simplicity and rapid onboarding.
	#'''Rapid Onboarding''' - one hour onboarding course for basic performance, and 4 hours for integrated process. One week (40 hours) for qualified process managers.		#'''Rapid Onboarding''' - one hour onboarding course for basic performance, and 4 hours for integrated process. One week (40 hours) for qualified process managers, who are ideally product owners.
	#'''Collaborators''' - who is collaborating? Need a team based on massive transformative purpose, where [[10x Is Easier Than 2x]]		#'''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.		#'''Documentation''' - most important asset. The OSE wiki is our repo.