Working Teams
Invitation Video
The target audience is new OSE Developers.
Script
We are developing (what are we doing) a high performing team (sets expectations clearly) of open source developers (it is not likely that those people who have not heard of open source have both the culture and technical literacy to work out) for a distributed, global development effort (scope is large). [footnote] r years, we have been working on the Global Village Construction Set, and have now developed Extreme Manufacturing techniques for building large machines in a single day, and for building houses in 5 days. We are improving our development process continuously, and our next step (aspiration) is building highly efficient working teams, minimum of 12 people each, that takes our development to 3-month product development cycles. This builds upon extensive prototyping and Proofs of Concept developed over the last 8 years and hudreds of prototypes in a dozen countries around the world. Our specific goal is Distributive Enterprise - open source blueprints for enterprises - on our way to creating the next trillion dollar economy - the open source economy. The power lies in open distribution of practical knowhow - raising the bar across all human fields of endeavor by open collaboration - an idea whose time has come.
Our promise to contributors is that of efficiency. We provide basic training that puts every person on the same page in terms of the OSE development platform. We teach basic skills such as CAD, and follow a formal open source product development process based on modular design and concurrent engineering. Process managers oversee the development process to to achieve timelines and results. We expect professional and constructive behavior. We recruit on an ongoing basis for 3-month project sprints, with a minimum volunteering commitment of 10 hours per week.
We develop technology by using an open participatory process the core tool that we use is the wiki witch like Wikipedia is open to editing by anybody where we can upload our pictures work logs documents each person on the team keeps a work log such that any other person on the team and can see transparently what anyone else is doing working teams are typically 12 people and we develop all the different steps of the open-source product development process as Guided by the development spreadsheet. Instructions are found for every step of the development process with key tools being used such as free CAD computer aided design embeddable Google Docs for real-time collaboration and kdenlive for video editing. We are looking for not only technically minded people to help develop our Technologies but also individuals such as writers video editors documentaries and just about anything else because of the scope of the global village Construction Set this to build a new civilization we train people by providing open source 101 instructional tunnel the topics of development including design guides for things like the 3D printer construction site or the tractor construction set we approach projects in a concurrent Engineering Process meaning massive parallel development as we break down Technologies into modules so that different teams and people can work in parallel we build and prototype continuously using Xtreme manufacturing one day builds as the culmination of the development process and finally we Produce open business models for producing any of our machines and one day with extreme manufacturing meaning of group-based social production build that is fun educational inspiring and productive.
Team Requirements
OSE is pursuing development of high performing teams as it moves into 2017. Each team needs to have a minimum level of staffing in order to perform at a high level. The recruiting process will continue until a basic team consisting of Process Manager, Specific (to a particular project) Product Owner, and Engineering Team are secured - in addition to the General Heavyweight Product Manager (xPM - for Extreme Product Manager). This basic team must be a minimum of 3 people in number - not counting the
The Specific Product Owner is required to have full knowledge of requirements for a project, including how the project fits within a product ecology of other projects. The Engineering Team and Process Manager produce documentation, unless a more dedicated Documentation Team is secured. It is understood that Human Resources (HR) works in the background to recruit additional team members - where HR must be sufficiently familiar with Process Management to understand which roles need to be filled in. Curriculum Development must occur prior to a team being formed - as new team members need to be brought up to speed. Curriculum Development includes toolchain instructionals, as well as Design Guides - which team prospective team members about design of a given project. Even experienced Product Designers benefit from the Design Guides - as the OSE version will typically be different than industry standard design. And prior to curriculum being developed for onboarding - the IT Team must have the OSE ISO ready so that everyone has full access to the OSE software stack.
Here are the roles defined:
- Process Manager- a person who understands the development process of open hardware, as embodied in the Development Template. Assures that both development and its documentation occurs. Maintains
- Product Owner - stakeholder who is interested in developing a Distributive Enterprise around a given hardware project.
- Engineering Team - doing CAD, calculations, and