OSE Develoment Task Assistance - Revision history

Marcin: /* Collaboration Protocol */

2018-02-27T18:03:51Z

Collaboration Protocol

← Older revision		Revision as of 18:03, 27 February 2018
Line 48:		Line 48:
	#Hosting a [[Design Sprint]] with 100 people to develop the next design and to publish the design in a Product Manual.		#Hosting a [[Design Sprint]] with 100 people to develop the next design and to publish the design in a Product Manual.
	#Adding the product to a collaborative production website (only minor tools required for assembly), and anyone benefitting from the sales and delivery of the product.		#Adding the product to a collaborative production website (only minor tools required for assembly), and anyone benefitting from the sales and delivery of the product.

			For successful Design Sprints, we need a complete Development Template protocol set to be defined, along with a tutorial on all the steps - such that 100 people minimum can work effectivele in parallel via a 1 day per month commitment.

Marcin at 18:02, 27 February 2018

2018-02-27T18:02:08Z

@@ Line 1: / Line 1: @@
 =Introduction=
-The key to rapid development is modular design with parallel development. When projects can be broken down into small tasks, many people can work on them in parallel. The critical part here is to share a language of collaborative literacy, which enables everyone to understand the status of what has been done and what needs to be done:
+The key to rapid development is modular design with parallel development. When projects can be broken down into small tasks, many people can work on them in parallel. The point is that modular design and parallel development depend fundamentally on the ability to coordinate development tasks. Thus, in augmented development practice, it crucial to learn the skills of collaboration - to gain a fluency in this skill - which we call [[Collaborative Literacy]].
 #How to break down a project into individual tasks. This means how machine systems, machines, modules, and parts can be broken down
@@ Line 21: / Line 23: @@
 If the above can be understood in detail, it can be automated, such that artificial intelligence can guide the process, and the process can possibly be tracked on a distributed ledger.
-Collaboration between open source projects works well when 2 projects are working in the same area - and tasks can be broken up for different people to work on them. However, many open source developers are [[Autistic Sociopaths]] - defined as cultural creatives who are so focused and absorbed in their work that they may not notice other external or social input coming their way.
+Collaboration between open source projects works well when two projects are working in the same area - and tasks can be broken up for different people to work on them. However, many open source developers are cultural creatives absorbed in their work to the point that working with others is difficult for various reasons.
-Are you working on an open source hardware development project? OSE can help if you are able t
+#They port their design to [[FreeCAD]]

Marcin at 17:32, 27 February 2018

2018-02-27T17:32:29Z

← Older revision		Revision as of 17:32, 27 February 2018
Line 21:		Line 21:
	If the above can be understood in detail, it can be automated, such that artificial intelligence can guide the process, and the process can possibly be tracked on a distributed ledger.		If the above can be understood in detail, it can be automated, such that artificial intelligence can guide the process, and the process can possibly be tracked on a distributed ledger.

	Collaboration between open source projects works well when 2 projects are working in the same area - and tasks can be broken up for different people to work on them. Are you working on an open source hardware development project? OSE can help if you are able t		Collaboration between open source projects works well when 2 projects are working in the same area - and tasks can be broken up for different people to work on them. However, many open source developers are [[Autistic Sociopaths]] - defined as cultural creatives who are so focused and absorbed in their work that they may not notice other external or social input coming their way.

			Are you working on an open source hardware development project? OSE can help if you are able t

Marcin: /* Introduction */

2018-02-27T17:24:09Z

Introduction

← Older revision		Revision as of 17:24, 27 February 2018
Line 1:		Line 1:
	=Introduction=		=Introduction=
	The key to rapid development is modular design with parallel development. When projects can be broken down into small tasks, many people can work on them in parallel. The critical part here is to share a language of collaborative literacy, which enables everyone to understand:		The key to rapid development is modular design with parallel development. When projects can be broken down into small tasks, many people can work on them in parallel. The critical part here is to share a language of collaborative literacy, which enables everyone to understand the status of what has been done and what needs to be done:

	#How to break down a project into individual tasks. This means how machine systems, machines, modules, and parts can be broken down		#How to break down a project into individual tasks. This means how machine systems, machines, modules, and parts can be broken down

Marcin: Created page with "=Introduction= The key to rapid development is modular design with parallel development. When projects can be broken down into small tasks, many people can work on them in par..."

2018-02-27T17:20:46Z

Created page with "=Introduction= The key to rapid development is modular design with parallel development. When projects can be broken down into small tasks, many people can work on them in par..."

New page

=Introduction=
The key to rapid development is modular design with parallel development. When projects can be broken down into small tasks, many people can work on them in parallel. The critical part here is to share a language of collaborative literacy, which enables everyone to understand:

#How to break down a project into individual tasks. This means how machine systems, machines, modules, and parts can be broken down
#When have contributions been made? This is done with timestamps, such as edit date on the wiki.
#Which tasks are done and which need doing. An automated platform that populates a scrum board with tasks should be produced. If a person is working on a task (as noted by an edit on a given development template), that person's name should populate the task automatically.
#What tools and resources are available for doing tasks
#What is the desirable order for task execution
#When to stop, continue, or iterate
#What is the 'definition of done,' ie, what constitutes completion
#Who is working on what tasks within the project
#Who are other groups doing related work?
#How are results communicated within and outside of the group?
#What skill sets are required to develop tasks?
#What skill sets/members does the project already have?
#What is the roadmap for a given project? What are the milestones for the project?
#Who is the project manager and product owner, and who is the team?
#What is the level of activity of the team? Github for example does this by showing an activity graph.
#What is the burndown of a project? This is already accessible at [[Burndown]] and linked automatically to the level of completion of a [[Development Template]].

If the above can be understood in detail, it can be automated, such that artificial intelligence can guide the process, and the process can possibly be tracked on a distributed ledger.

Collaboration between open source projects works well when 2 projects are working in the same area - and tasks can be broken up for different people to work on them. Are you working on an open source hardware development project? OSE can help if you are able t