Engineers for a Sustainable World Webinar - Revision history

Marcin: /* Section III - Development */

2013-11-20T21:03:00Z

Section III - Development

← Older revision		Revision as of 21:03, 20 November 2013
Line 19:		Line 19:
	#How does OSE develop its products? We follow principles of Extreme Manufacturing - an agile development model based on Extreme Programming. We are defining the meaning of Extreme Manufacturing: lean, test-driven, modular design - with emphasis on achieving Language Agnostic Instructional that results in parallel machine builds - in a single day. (show pictures of workshop and sparks)		#How does OSE develop its products? We follow principles of Extreme Manufacturing - an agile development model based on Extreme Programming. We are defining the meaning of Extreme Manufacturing: lean, test-driven, modular design - with emphasis on achieving Language Agnostic Instructional that results in parallel machine builds - in a single day. (show pictures of workshop and sparks)
	#To achieve single day builds, we apply Module-Based Design. We have 50 machines - and we break them down into about 10 modules each. (show [[Dozuki]] page). The key to our development methods is documentation, and we are pushing the limits of this by Real Time Documentation - a milestone which we have achieved in the last couple months. Our documentation platform looks like this ([[Dozuki]]). You can navigate to each of our 50 machines. Select a machine, and you see 4 main topics. The main topic is Modules - which is a tracker for all the development and documentation.		#To achieve single day builds, we apply Module-Based Design. We have 50 machines - and we break them down into about 10 modules each. (show [[Dozuki]] page). The key to our development methods is documentation, and we are pushing the limits of this by Real Time Documentation - a milestone which we have achieved in the last couple months. Our documentation platform looks like this ([[Dozuki]]). You can navigate to each of our 50 machines. Select a machine, and you see 4 main topics. The main topic is Modules - which is a tracker for all the development and documentation.
	~~'''~~#When you click on Modules - all the different Modules appear. (paste an image of the modules, such as for the Laser Cutter - into the [[Dozuki]] graphic - or start a new slide)		#When you click on Modules - all the different Modules appear. (paste an image of the modules, such as for the Laser Cutter - into the [[Dozuki]] graphic - or start a new slide)
	#For every module, we have a [[Development Board Template]]. This consists of 25 main development points that need to be taken for every machine. (see first page of [[Development Board Template]])		#For every module, we have a [[Development Board Template]]. This consists of 25 main development points that need to be taken for every machine. (see first page of [[Development Board Template]])
	#For every module - we also have other supporting steps - such as all the overall development steps total to about 75. (see first page of [[Development Board Template]] spreadsheet)		#For every module - we also have other supporting steps - such as all the overall development steps total to about 75. (see first page of [[Development Board Template]] spreadsheet)

Marcin: /* Section III - Development */

2013-11-20T21:02:51Z

Section III - Development

← Older revision		Revision as of 21:02, 20 November 2013
Line 19:		Line 19:
	#How does OSE develop its products? We follow principles of Extreme Manufacturing - an agile development model based on Extreme Programming. We are defining the meaning of Extreme Manufacturing: lean, test-driven, modular design - with emphasis on achieving Language Agnostic Instructional that results in parallel machine builds - in a single day. (show pictures of workshop and sparks)		#How does OSE develop its products? We follow principles of Extreme Manufacturing - an agile development model based on Extreme Programming. We are defining the meaning of Extreme Manufacturing: lean, test-driven, modular design - with emphasis on achieving Language Agnostic Instructional that results in parallel machine builds - in a single day. (show pictures of workshop and sparks)
	#To achieve single day builds, we apply Module-Based Design. We have 50 machines - and we break them down into about 10 modules each. (show [[Dozuki]] page). The key to our development methods is documentation, and we are pushing the limits of this by Real Time Documentation - a milestone which we have achieved in the last couple months. Our documentation platform looks like this ([[Dozuki]]). You can navigate to each of our 50 machines. Select a machine, and you see 4 main topics. The main topic is Modules - which is a tracker for all the development and documentation.		#To achieve single day builds, we apply Module-Based Design. We have 50 machines - and we break them down into about 10 modules each. (show [[Dozuki]] page). The key to our development methods is documentation, and we are pushing the limits of this by Real Time Documentation - a milestone which we have achieved in the last couple months. Our documentation platform looks like this ([[Dozuki]]). You can navigate to each of our 50 machines. Select a machine, and you see 4 main topics. The main topic is Modules - which is a tracker for all the development and documentation.
	#When you click on Modules - all the different Modules appear. (paste an image of the modules, such as for the Laser Cutter - into the [[Dozuki]] graphic - or start a new slide)		'''#When you click on Modules - all the different Modules appear. (paste an image of the modules, such as for the Laser Cutter - into the [[Dozuki]] graphic - or start a new slide)
	#For every module, we have a [[Development Board Template]]. This consists of 25 main development points that need to be taken for every machine. (see first page of [[Development Board Template]])		#For every module, we have a [[Development Board Template]]. This consists of 25 main development points that need to be taken for every machine. (see first page of [[Development Board Template]])
	#For every module - we also have other supporting steps - such as all the overall development steps total to about 75. (see first page of [[Development Board Template]] spreadsheet)		#For every module - we also have other supporting steps - such as all the overall development steps total to about 75. (see first page of [[Development Board Template]] spreadsheet)
Line 29:		Line 29:
	#and realtime video to Youtube. (show screenshots)		#and realtime video to Youtube. (show screenshots)
	#We use Latakoo for collaborative editing. (show screenshot)		#We use Latakoo for collaborative editing. (show screenshot)
	#Remote collaborators can then take the realtime uploaded media - and create instructionals in Dozuki - so that at the end of a build - an instructional is produced at the same time. This addresses a major issue - of documentation being created instead of lost in a documentation blackhole. (show a screenshot of an instructional)		#Remote collaborators can then take the realtime uploaded media - and create instructionals in Dozuki - so that at the end of a build - an instructional is produced at the same time. This addresses a major issue - of documentation being created instead of lost in a documentation blackhole. (show a screenshot of an instructional)'''
	#The above refers to remote design collaboration - in the form of sprints. (screenshot)		#The above refers to remote design collaboration - in the form of sprints. (screenshot)
	#On site, we host Dedicated Project Visits - which are typically 1 month long. If you are interested in a summer or break project or other independent study or class project - we invite you on site. (show a group shot with microhouse)		#On site, we host Dedicated Project Visits - which are typically 1 month long. If you are interested in a summer or break project or other independent study or class project - we invite you on site. (show a group shot with microhouse)

Marcin: /* Section II - Overview of Development */

2013-11-20T21:00:33Z

Section II - Overview of Development

← Older revision		Revision as of 21:00, 20 November 2013
Line 11:		Line 11:
	=Section II - Overview of Development=		=Section II - Overview of Development=

	Take slides 50-60 from [[OHS Presentation]]. See Open Hardware Summit Script - [[OHS_Presentation#Script]]		Take slides 50-60 (as in script above) from [[OHS Presentation]]. See Open Hardware Summit Script - [[OHS_Presentation#Script]]

	Then we can go into more specifics -		Then we can go into more specifics -

Marcin: /* Section I - Based on Open Source Hardware Summit */

2013-11-20T20:57:57Z

Section I - Based on Open Source Hardware Summit

← Older revision		Revision as of 20:57, 20 November 2013
Line 5:		Line 5:
	[https://docs.google.com/a/opensourceecology.org/document/d/1AdbwCAtPhgkqdMYlVrlJPM3pwFjYqvw7OQzCD5I53JA/edit edit]		[https://docs.google.com/a/opensourceecology.org/document/d/1AdbwCAtPhgkqdMYlVrlJPM3pwFjYqvw7OQzCD5I53JA/edit edit]

	Take up to Slide 42 ~~from~~ the above. Then add your PowerPoint slides 52-62. (From today)		Take up to Slide 42 as in the script above. Then add your PowerPoint slides 52-62. (From today)

	Then:		Then:

Marcin: /* Summary */

2013-11-20T20:54:26Z

Summary

← Older revision		Revision as of 20:54, 20 November 2013
Line 34:		Line 34:
	#On site - our goal is to achieve up to language agnostic instructionals - where a team of about 12 people can build each of our machines in a single day. This is a great challenge - but we have already shown it for our brick press - 12 people did that on Dec 18 of 2012.		#On site - our goal is to achieve up to language agnostic instructionals - where a team of about 12 people can build each of our machines in a single day. This is a great challenge - but we have already shown it for our brick press - 12 people did that on Dec 18 of 2012.

	=Summary=		=Section IV - Summary=

	Sum up why are we doing this? Open hardware is important. 80% slide. Show slide 58 and 60 from [https://docs.google.com/a/opensourceecology.org/document/d/1AdbwCAtPhgkqdMYlVrlJPM3pwFjYqvw7OQzCD5I53JA/edit].		Sum up why are we doing this? Open hardware is important. 80% slide. Show slide 58 and 60 from [https://docs.google.com/a/opensourceecology.org/document/d/1AdbwCAtPhgkqdMYlVrlJPM3pwFjYqvw7OQzCD5I53JA/edit].

Marcin: /* Script for Section on Development */

2013-11-20T20:54:16Z

Script for Section on Development

← Older revision		Revision as of 20:54, 20 November 2013
Line 15:		Line 15:
	Then we can go into more specifics -		Then we can go into more specifics -

	=~~Script for~~ Section on Development=		=Section III - Development=

	#How does OSE develop its products? We follow principles of Extreme Manufacturing - an agile development model based on Extreme Programming. We are defining the meaning of Extreme Manufacturing: lean, test-driven, modular design - with emphasis on achieving Language Agnostic Instructional that results in parallel machine builds - in a single day. (show pictures of workshop and sparks)		#How does OSE develop its products? We follow principles of Extreme Manufacturing - an agile development model based on Extreme Programming. We are defining the meaning of Extreme Manufacturing: lean, test-driven, modular design - with emphasis on achieving Language Agnostic Instructional that results in parallel machine builds - in a single day. (show pictures of workshop and sparks)

Marcin: /* Overview of Development */

2013-11-20T20:53:58Z

Overview of Development

← Older revision		Revision as of 20:53, 20 November 2013
Line 9:		Line 9:
	Then:		Then:

	=Overview of Development=		=Section II - Overview of Development=

	Take slides 50-60 from [[OHS Presentation]]. See Open Hardware Summit Script - [[OHS_Presentation#Script]]		Take slides 50-60 from [[OHS Presentation]]. See Open Hardware Summit Script - [[OHS_Presentation#Script]]

Marcin: /* First Part of Talk - Based on Open Source Hardware Summit */

2013-11-20T20:53:47Z

First Part of Talk - Based on Open Source Hardware Summit

← Older revision		Revision as of 20:53, 20 November 2013
Line 1:		Line 1:
	=~~First Part of Talk~~ - Based on Open Source Hardware Summit=		=Section I - Based on Open Source Hardware Summit=

	<html><iframe src="https://docs.google.com/document/d/1AdbwCAtPhgkqdMYlVrlJPM3pwFjYqvw7OQzCD5I53JA/pub?embedded=true" width=100% height=500></iframe></html>		<html><iframe src="https://docs.google.com/document/d/1AdbwCAtPhgkqdMYlVrlJPM3pwFjYqvw7OQzCD5I53JA/pub?embedded=true" width=100% height=500></iframe></html>

Marcin: /* Summary */

2013-11-20T20:53:27Z

Summary

← Older revision		Revision as of 20:53, 20 November 2013
Line 36:		Line 36:
	=Summary=		=Summary=

	Sum up why are we doing this? Open hardware is important. 80% slide		Sum up why are we doing this? Open hardware is important. 80% slide. Show slide 58 and 60 from [https://docs.google.com/a/opensourceecology.org/document/d/1AdbwCAtPhgkqdMYlVrlJPM3pwFjYqvw7OQzCD5I53JA/edit].

Marcin: /* Script for Section on Development */

2013-11-20T20:52:29Z

Script for Section on Development

← Older revision		Revision as of 20:52, 20 November 2013
Line 17:		Line 17:
	=Script for Section on Development=		=Script for Section on Development=

	#How does OSE develop its products? We follow principles of Extreme Manufacturing - an agile development model based on Extreme Programming. We are defining the meaning of Extreme Manufacturing: lean, test-driven, modular design - with emphasis on achieving Language Agnostic Instructional that results in parallel machine builds - in a single day.		#How does OSE develop its products? We follow principles of Extreme Manufacturing - an agile development model based on Extreme Programming. We are defining the meaning of Extreme Manufacturing: lean, test-driven, modular design - with emphasis on achieving Language Agnostic Instructional that results in parallel machine builds - in a single day. (show pictures of workshop and sparks)
	#To achieve single day builds, we apply Module-Based Design. We have 50 machines - and we break them down into about 10 modules each.		#To achieve single day builds, we apply Module-Based Design. We have 50 machines - and we break them down into about 10 modules each. (show [[Dozuki]] page). The key to our development methods is documentation, and we are pushing the limits of this by Real Time Documentation - a milestone which we have achieved in the last couple months. Our documentation platform looks like this ([[Dozuki]]). You can navigate to each of our 50 machines. Select a machine, and you see 4 main topics. The main topic is Modules - which is a tracker for all the development and documentation.
	#The key to our development methods is documentation, and we are pushing the limits of this by Real Time Documentation - a milestone which we have achieved in the last couple months.
	#Our documentation platform looks like this ([[Dozuki]]). You can navigate to each of our 50 machines. Select a machine, and you see 4 main topics. The main topic is Modules - which is a tracker for all the development and documentation.
	#When you click on Modules - all the different Modules appear. (paste an image of the modules, such as for the Laser Cutter - into the [[Dozuki]] graphic - or start a new slide)		#When you click on Modules - all the different Modules appear. (paste an image of the modules, such as for the Laser Cutter - into the [[Dozuki]] graphic - or start a new slide)
	#For every module, we have a [[Development Board Template]]. This consists of 25 main development points that need to be taken for every machine. (see first page of [[Development Board Template]])		#For every module, we have a [[Development Board Template]]. This consists of 25 main development points that need to be taken for every machine. (see first page of [[Development Board Template]])
Line 26:		Line 24:
	#But here we will focus on the 25 most critical ones. (I will go through each step)		#But here we will focus on the 25 most critical ones. (I will go through each step)
	#Once a step is completed - the results are placed on the OSE wiki - and a link to that wiki page is put in the LINK TO WORK AND PRODUCTS column of the Development Board.		#Once a step is completed - the results are placed on the OSE wiki - and a link to that wiki page is put in the LINK TO WORK AND PRODUCTS column of the Development Board.
	#The point of this technique is that we can design products not as entire entities - but as an assembly of modules - where each module is developed independently. So for example - in the ideal case - we would have a team of 12 people working on each module to fill in all the required development point - and we would have a dozen of such teams - such that on a single day - a team of about 100 engineers could design a complete machine in a single day.		#The point of this technique is that we can design products not as entire entities - but as an assembly of modules - where each module is developed independently. So for example - in the ideal case - we would have a team of 12 people working on each module to fill in all the required development point - and we would have a dozen of such teams - such that on a single day - a team of about 100 engineers could design a complete machine in a single day. I would like to propose that we take 12 ESW chapters - and do exactly that - a weekend sprint - where we do a complete design in a day and then get ready for a build. Whe here would like to try this and help me organize this? I am looking for 12 chapter leader that could help me do this. The way I could see this is that we have a planning meeting with chapter leaders, who go back to their respective team - and propose a given project. Then we prepare, and host a design day with a dozen chapters working in parallel.
	#I would like to propose that we take 12 ESW chapters - and do exactly that - a weekend sprint - where we do a complete design in a day and then get ready for a build. Whe here would like to try this and help me organize this? I am looking for 12 chapter leader that could help me do this.		#Now we go back to some more mechanics. Each collaborator keeps a [[Work Log]]. (show screenshot of worklog wiki page)
	#The way I could see this is that we have a planning meeting with chapter leaders, who go back to their respective team - and propose a given project. Then we prepare, and host a design day with a dozen chapters working in parallel.		#Each collaborator, if they are doing a build on site - uploads pictures to trovebox, (show screenshots)
	#Now we go back to some more mechanics. Each collaborator keeps a [[Work Log]]. Each collaborator, if they are doing a build on site - uploads pictures to trovebox, and video to Youtube.		#and realtime video to Youtube. (show screenshots)
	#Remote collaborators can then take the realtime uploaded media - and create instructionals in Dozuki - so that at the end of a build - an instructional is produced at the same time. This addresses a major issue - of documentation being created instead of lost in a documentation blackhole.		#We use Latakoo for collaborative editing. (show screenshot)
	#The above refers to remote design collaboration - in the form of sprints.		#Remote collaborators can then take the realtime uploaded media - and create instructionals in Dozuki - so that at the end of a build - an instructional is produced at the same time. This addresses a major issue - of documentation being created instead of lost in a documentation blackhole. (show a screenshot of an instructional)
	#On site, we host Dedicated Project Visits - which are typically 1 month long. If you are interested in a summer or break project or other independent study or class project - we invite you on site.		#The above refers to remote design collaboration - in the form of sprints. (screenshot)
			#On site, we host Dedicated Project Visits - which are typically 1 month long. If you are interested in a summer or break project or other independent study or class project - we invite you on site. (show a group shot with microhouse)
	#On site - our goal is to achieve up to language agnostic instructionals - where a team of about 12 people can build each of our machines in a single day. This is a great challenge - but we have already shown it for our brick press - 12 people did that on Dec 18 of 2012.		#On site - our goal is to achieve up to language agnostic instructionals - where a team of about 12 people can build each of our machines in a single day. This is a great challenge - but we have already shown it for our brick press - 12 people did that on Dec 18 of 2012.

			=Summary=

			Sum up why are we doing this? Open hardware is important. 80% slide