OSE Design Sprint
- 1 About
- 2 2020
- 3 2018
- 4 Prerequisite
- 5 2016 Update
- 6 2015 Update
- 7 OSE Design Sprints Introduction Video from 2013
- 8 MicroHouse 4 Design Sprints - August 2014
- 9 Design Sprint Resources
- 10 Publishing Standards
- 11 Ideal Design Sprint
- 12 More Information
Design Sprints are large-scale collaborative events where OSE engages in Public Design of goods and services for solving pressing world issues. For solving pressing world issues? Yes, the 17 Sustainable Development Goals (SDGs). How do goods and services solve for SDGs? SDGs are largely material in nature, thus creating products with added ethical content is a way to address pressing world issues. For example, to zero hunger we need to grow food - and more importantly - access to food. The same goes for most tangible products. Production is not as important as widespread access. Only an ethical economy assures widespread access - which means that in addition to solving product design - OSE solves for business models that facilitate equitable access to and wide distribution of the goods. It's been said that the 'future is unevenly distributed.' OSE's intent is to address progress in a more distributed way - ie - where more people have access to progress. Design Sprints are one way that OSE creates access, as a basis for distributed production models.
What's new in 2020? We are migrating to carefully architected, large-scale, collaborative events according to the principles of Extreme Enterprise. This solves for sufficient skill sets showing up to reach completion of projects in rapid time. To date, we've been able to get up to 20 people to show up to remote design sprints. We need 2000, and such large numbers are what the Extreme Enterprise concept is intended to solve.
Please spend 2 hours to learn FreeCAD prior to joining any design spring - OSE_FreeCAD_Tutorials
We plan on hosting Design Sprints once version 0.01 of the OSE Open Source Product Development Platform is created. This involves integrating various tools and processes that OSE has been using into a coherent whole.
For reorganizing the wiki, we need improved templates. One useful template is the one for Backhoe Development - see OSE-OSHW-Dev-Backhoe - which was used before - can we update this to a full working template where we pass parameters into the template so we can display what we need in each window?
See the blog post which reflects some of our techniques - http://opensourceecology.org/ose-design-sprints-spur-innovation/.
All the learnings from the past years, such as realtime documentation, module based design, extreme manufacturing, test-driven design, the development spreadsheet - and now adding FreeCAD to our list of stable tools with its tractor construction set part library and workbench - will be absorbed into the OSE Design Guide - a training guide for potential developers. This Guide will be a prerequisite to hosting future Design Sprints.
We are kicking off this year's design sprints with work on the Open Source Technology Pattern Language Icons. See above.
OSE Design Sprints Introduction Video from 2013
To sign up, fill out the Tech Team Culturing Survey to be put on our email list, where we email participants with announcements on all Design Sprints.
We are also creating collaborative video editing infrastructure similar to OSEdit to go with the OSE Design Sprints. Sign up also at the Tech Team Culturing Survey for remote video editing - make sure to mark Video Editor in skill section.
MicroHouse 4 Design Sprints - August 2014
Dear Design Sprinters,
As part of our MicroHouse 4 Workshop - we are pushing the limits of global collaborative design. We are calling all builders, architects, designers, sketchup users, and technical writers to participate in a 4 week flurry of Design Sprints.
We are preparing for a seamless build of MicroHouse 4 - our most ambitious build yet. Aanouncement forthcoming.
To deliver on the radical efficiency key to OSE’s values - we are calling for a global design sprint where we invite you to participate in the production of the instructionals and teaching material so clear and complete that we deliver on our promise of a civilization starter kit - a set of blueprints to critical infrastructure technologies - built in the most simple and efficient way.
The MicroHouse is one part of it.
This time around - we will be optimizing 2 things: the CEB wall build, and roof build. The wall is a general wall system that can be applied to many structures. The roofing system consists of modular, 3’x16’ panels that can be built quickly, and light enough that they can be installed in minutes. To do this, we are paying special attention to interfaces such that panels can be joined in a few minutes, while closing air gaps tightly. This system is intended to provide a generalized wall-floor-window-door-roof system that can be applied to any construction.
To achieve this, we are producing Sketchup libraries of component details - that allow anyone who can manipulate objects in Sketchup to put together their own house.
With your help, the world will receive clear instructionals on how to do this. We aim to make our CEB building technique so streamlined that it’s truly replicable by many people. The modules we are building are relevant to tiny homes of 144 square feet in area - and to larger ones - like the current one - at 750 square feet. This existing structure will become work space and office space.
The process here revolves around people studying our design concepts and assets, building on prior work, and producing the next iteration of design detail. Much of it is converting concept designs to detailed instructionals and Sketchup details. We are welcoming anyone who has a good sense of practical build experience - and who is willing to work as a team to make the build happen.
To join us, see above for the location of the Google Hangout. See our main Planning Document - https://docs.google.com/a/opensourceecology.org/presentation/d/1ZfrvXvAP8u8e7hrkF55pZuakQkJRRPKJPb4K3w-2HmA/edit#slide=id.p
Design Sprint Resources
- For 3D Design work, OSE primarily uses Sketch Up. Sketch Up can be downloaded free here. Click here for a quick Sketch Familiarization Tutorial.
- Design Sprint participants are asked to create a work log. See Wiki instructions for information on how to create a page, load files, and write in "wiki." See Jonathan Log for an example work log.
- To contact other Design Sprint participants, see Design Sprint Members.
- See Design Sprint FAQ for answers to common questions.
If you have questions about Design Sprints and participation, please contact firstname.lastname@example.org
So, You Think That You Need to be an Engineer to Contribute to our Lifesize Lego Set?
Wrong. While naturally inspired leadership and some of the world's leading subject matter experts are contributing to the project - there are numerous points of entry for any contributor who can merely surf the web - or for someone who can learn basic proficiency in Sketchup in about 2 hours using our Sketchup Howto and Official OSE Warehouse of stock parts (primarily plate and tubing).
First, you have to understand OSE Design Principles and Module Based Design. This means that we break down machines into the largest possible number of modules that can be developed in parallel. For this to work, we need to specify how the modules fit together to make a complete machine - which is called interface design. Before people start working on the technical design of modules, they need to be very clear about how the modules fit together.
If you have no skills other than surfing the web but you do have some technical knowhow (you are a farmer, builder, or any other hands-on producer) - you can get busy with defining conceptual diagrams of all the parts that go into a machine. You can then start defining how these parts fit together. Even if you have no technical knowhow - you can search for images of a given device and paste those images into a google drawing as a study of Industry Standards - how others are building the machines. That is useful as a background study - as is a study of patents to show various ways in which designs have been implemented.
If you are a graphics artist - you can draw up Infographics on a machine - or icons for the submodules that we are working on.
If you have some technical experience, you can help us post challenges on GrabCAD, or you can help us document at Dozuki, or you can help organize our main wiki machine pages - especially if you can create a useful template that all of machines can follow.
Further Details (work in progress)
- Concept. The basic process starts with a Concept. This applies to each of the 50 GVCS machines. The concept is a simple set of specifications that list basic parameters, focusing on OSE Specifications. The Concept is just written text - and it constitutes the OSHW Dashboard for a given project.
- Breakdown into Modules - In Module Based Design, products are broken into the smaller components that can be produced independently and then assembled together to the finished machine. The advantage of Module Based Design is that teams can work on different parts of a machine at the same time - without bottlenecks of dependence on prior steps typical of a linear production sequence. This breakdown is called the Systems Engineering Breakdown Diagram, and it can be represented as a simple Google Doc with bubbles that correspond to each component and arrows that link the components together. When breaking a machine into modules, the point to keep in mind should be into what small est part can I break the complete machine down.
- Interface Design - It would be impossible to break down the machine into modules - and try to assemble the modules together - without understanding how the modules fit with one another. This means - what is the interface between the modules? The interface could be something like dimensions of an object or a bolt pattern of how 2 modules fit together, or it could be a specification of a connector type - such as a USB cable that links 2 electronics items together. An interface diagram should be one or several Google Drawings embedded in a wiki page - with a graphical representation showing the dimensions, connection types, etc.
When documenting, participants should set up a Work Log, such as Marcin Log. Google Docs should be embedded as they are created, with an edit link for editing the Google Doc. This way, updates are made automatically on the wiki, and the document is accessible immediately via an edit link. Google Doc Presentations should be used when there are many pages of a document - such as a build procedure that comes out of an exploded part diagram.
Ideal Design Sprint
A design sprint should have these contributors outside of the Sprint Master. We are testing a method where we script in 8 one hour sessions (Sprint Topics) on a design sprint 8 hour day where each hour is dedicated to a specific machine or a related set of modules. The following lists 70 individuals that can participate in each Sprint Topic (machine or set of related modules), and 24 further individuals who engage in documentation and sprint-improvement metaservices. This brings the total sprint participation goal to 70*8 = 560 + 24 = 584 participants sought for every Saturday design sprint.
Participants for every Sprint Instance on Mechanical Devices:
-  Sprint Master - Directs people to the necessary tasks. 1 Sprint Master needed. If there is more than one, this Sprint Master should set up their own Sprint Session. Sprint Master prepares a 1 paragraph-1 page Brief to
- Module-Based Design Breakdown (SEBD -Systems Engineering Breakdown Diagram)- breaking down every machine into the smallest components possible. Participants scour the internet for industry standards, and also consult the OSE wiki for content. See CEB Press at Dozuki for the brick press broken down into small components. 6 people could easily work on a large Google Drawing in realtime to fill in each component. Subject matter experts and heavy users of machine can do this.
-  Graphics artist creates graphical icons for each of the modules defined in the SEBD
-  Interface Design - Once modules are specified, it should be made clear how they fit together. This could be a realtime Google Drawing of conceptual modules from the SEBD, emphasizing the interfaces between modules and providing qualitative and quantitative description of the interface. Screenshots of machine parts from CAD or online pictures could also be used to create an Interface Design.
-  A graphics artist could make concise infographics to make concepts transparent. Concepts needed are (1) how the machine works, (2) different types of machines, (3) their relevance and statistics around the machine, and many other pieces of content that any skilled graphics artist can represent in a user-friendly way.
-  Animator - takes existing Sketchup files and makes informative Functional Videos. This could be done for every machine or module.
-  Archivist - scours Blog, Prototypes Built and Cost, and YouTube/Vimeo for presenting all prior work on a given project. Documents at Dozuki.
-  Engineers - provide Calculations and CAE analysis for each module.
-  Electronics - Arduino controllers for things like CEB Press Controller and drone/ computer vision tractors
-  Machinists/ Tool and Die Makers - writing procedures of how to fabricate certain parts from scratch, including items such as hardened blades or sprockets.
-  Hydraulic Power Experts - draw up formal Hydraulics Diagrams.
-  Hydraulics Nonexperts - individuals who watch Hydraulics 101 and produce visual hydraulics assembly diagrams.
-  Sketchup Novices - people who take near-final designs and create exploded parts diagrams with labels, and who create step-by-step procedures for building
-  2D CAD people - individuals who use LibreCAD to create DXF torch table cutting files for all parts to be cut via CNC plasma cutter or laser cutter
-  3D printing people - people who generate optimized g-code files for specific 3D printing platforms, document these, and print them for purposes of rapid prototyping. These components will be taken from the OSE Warehouse
-  Laser cutting people - people who
-  Technical writer/blogger - person who interviews all contributors throughout the Sprint Topic to write a blog post on the event.
Special Sprint - Video and Documentation:
-  Director - directs media production efforts
-  Video Editor - takes existing footage and turns it into Instructional or Eye Candy Videos
-  Script Writer - writes a scripts on the machine under development
-  Dozuki Master - scours Design Sprint participant Logs (linked from Dashboard)
-  CSS/HTML - person who produces an improved Design Sprint Wiki Template for the Dashboard
-  CSS/HTML - a person who produces an improved Design Sprint Module Documentation template for each module, and who populates the module with content
Special Sprint - Metasprint
-  Recruiter - A person who works with OSE Technical Community Manager on identifying and recruiting talent for further Design Sprints, and who leverages social media to recruit.
-  GrabCAD master - a person who scours existing problem statement and publishes a parallel challenge on GrabCAD
-  Channeling Fairy - a person who engages RepRap IRC
-  Graphics artist - creates badge icons for the wiki for each type of contribution
-  Constant Quality Improvement professional - Evaluates existing process and publishes improvements to Design Sprint Protocol.
-  Uberblogger or Blog Master - a person who interviews the 8 Event Bloggers to write up a more general-audience blog post on each design sprint.