Engineers for a Sustainable World Webinar
Section I - Based on Open Source Hardware Summit
Take up to Slide 42 as in the script above. Then add your PowerPoint slides 52-62. (From today)
Section II - Overview of Development
Then we can go into more specifics -
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)
- 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)
- 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)
- 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.
- 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.
- Now we go back to some more mechanics. Each collaborator keeps a Work Log. (show screenshot of worklog wiki page)
- Each collaborator, if they are doing a build on site - uploads pictures to trovebox, (show screenshots)
- and realtime video to Youtube. (show screenshots)
- 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)
- 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.
Section IV - Summary
Sum up why are we doing this? Open hardware is important. 80% slide. Show slide 58 and 60 from .