- 1 Introduction
- 2 Usage
- 3 Process Map
- 4 Development Platform Ecology
- 5 Instructions for Using the Development Template
- 6 Process Manager
- 7 Development Template Requirements
- 8 Process Development
- 9 Older Templates
- 10 Notes
- 11 Extended Template
- 12 Layers
- 13 Links
OSE follows an Open Source Product Development process that is based on OSE Specifications of modularity, scalability, and agility. We follow a Construction Set Approach, where instead of making individual products, we create construction sets for many products. We are developing a Distributive Enterprise economic model. We use the Development Template as a list of steps required to deliver a complete product.
Use the following template to document all of the deliverables of an Open Source Product Development process. This template has multiple viewpoints according to the Zachman Ontology concept, with the different tabs at the bottom representing the different views. this template follows module based design in that this template is used for every module and each module can be defined at any Depth of Modularity. We start with a breakdown of a machine by modules, and then we break each module into the following ~40 elements. Some modules may be used in many machines.
As of 2015, OSE is reframing development around modules, not machines. For example - the tracks for heavy equipment are a critical module that can be used in many heavy machines - so as opposed to developing a Bulldozer, one may choose to develop the tracks by treating the tracks as a multipurpose component. This helps to maintain the multipurpose flexibility of modules and improves the Product Ecology of the GVCS.
Note that the template below mixes process and technical development steps somewhat, and this needs to be reconciled.
Based on the Development Template, here is a broader Development Process Map + parallelization strategy of workflow for development:
Development Platform Ecology
Instructions for Using the Development Template
Click Edit below the spreadsheet above - and then make a copy of the Spreadsheet. Then start filling the spreadsheet with development work. For the "Link to Work Product" in the spreadsheet, create a link that goes to the wiki page with the content. In the red column, type 1-10 for the level of completion of that step.
This way, anyone can fork or start a development project. We suggest starting a Work Log so anyone can see what anyone else on the team is doing.
The Process Manager is someone selected from the OSE Developer team who takes on additional management responsibility in addition to normal development tasks. There are 2 main aspects. First, is a checklist of day-to-day tasks, and the second is guiding a Working Team in terms of overall direction. The goal of the Process Manager's role in guiding Working Teams is to free the Heavyweight Product Manager (HPM) as much as possible so that the HPM can fulfill their role of managing the overall project, consisting of many Working Teams. A Working Team could in principle be started for each of the different GVCS Modules, of which there is a total of approximately 500.
Process Management Checklist
The checklist for the Process Manager's role is assuring that these tasks are accomplished:
- Helps orient new Working Team members - Welcome Email
- Pairs up developers in groups of 2 as the basic unit of team organization. Pairs collaborate on working tasks. Working in pairs comes from software's Extreme Programming agile methodology, and assures that visible progress is occuring even if one person is not availabe. This method also allows a Working Team to reach 24 members while remaining manageable. Both team members are expected to participate in the Weekly Project Meeting (typically Monday 11 AM CST) .
- Maintenance of the Logs page. Both New OSE Developers' logs and any new project logs are added to the Logs page.
- Each OSE Developer maintains a log of their weekly activity as[[Developer Name Log]]
- Each OSE Developer fills out a weekly Time Sheet
- Coordinates with HR on additional roles/members needed for each team. Coordinates with HR on hiring/firing decisions. Any firing decisions are made upon the OSE Developer missing 3 or more of the 12 weekly assignments in any 90 day development period.
- Keeps notes on the Weekly Meeting in the Project Meeting Log. Documents the task assignment for each Project Meeting.
- Tracks the official start dates of OSE Developers. Developers are accepted on an ongoing basis upon completing the OSE FreeCAD Test, for a 90 day duration. If Developers are applying for a future date - the beginning of a quarter is a good start date - or June 1 for college students.
- Teams start with the minimum of 4 roles: Heavyweight Product Manager, Process Manager, Product Owner, and Development Team
- If team reaches 12 pairs, a new team should be started. The Process Manager facilitates training of a new Process Manager for a new team.
- Process Managers study the Development Template on an ongoing basis to understand the development workflow. The Process Manager Certification will be released after the first 90-day development cycle. Certified Process Managers are responsible for selecting and training new process managers. OSE's goal is to double the number of 12 pair working teams after every 90 day Development Cycle.
- maintains a burndown graph based on the Development Template completion status
- Adds links to the Work Product column of Development Template
Process Management Training
While the Process Management Checklist above is relatively straightforward, and can be carried out relatively easily, guiding the development process itself according to the Development Template can be much more challenging. For this, a detailed narrative and extensive hands-on training (3 months minimum) is required. Here is a draft of the Process Management Traiing.
Development Template Requirements
- Works from the perspective of Module Based Design
- Scalable to thousands of new contributions per month
- Allows for immediate forking of projects on the module level
- Is autonomous in that entire development is explained
- Development process is fractal and modular. The whole development process is embodied for a system, machine, module, and part.
- Edit is transparent. Development team can be contacted readily.
- New people can join the project directly without any barriers.
- Credit is given to contributors
- Merit is established by the number of contributions
- Explainer videos are used throughout to train developers
- Icons are created for all systems, machines, modules, parts, and also for the full range of Zachman Framework Perspectives
In 2013 we formulated the Development Board and have made small improvememnts in 2014. At the end of 2014, we are revisiting the Development Process:
Development Template Metrics
The Development Boards (Dev Boards) are OSE's documentation. This documentation involves a comprehensive template (Dev Template) of items necessary for the directed development of products and services.
OSE is currently using the Dev Boards on the development of OSE's technologies. OSE's focus is the 50 machines of the Global Village Construction Set (GVCS) . At the same time, OSE intends to develop a generalized platform applicable to the development of any goods, services, product systems, or Product Service Systems [ref].
Success of the Development Boards may be defined by their contribution to the open source economy:
- How effectively the Dev Boards are getting completed. In other words, how effectively product are being developed
- How effectively do the Dev Boards result in technology transfer. In other words, after the product development is complete, is the product being replicated and produced towards creating an ethical economy. (The term Ethical Economy must be defined). Is the know-how leading to economic activity?
- How effectively are new tools and ecosystems being created for improving the effectiveness of product development using the Dev Boards
- How much adoption is occurring by other people or projects adopting the OSE development techniques for developing their products? Are people using the Dev Board spreadsheets or the specific protocols in the Dev Board spreadsheets to develop their products in an open source context?
- Speed of market saturation of a given field of productive endeavor
The last is the ultimate metric of success. It assumes a 'rational marketplace' where the greatest number of people benefit - a condition which may not be available in today's society. OSE's assumption is that there is potential of bypassing an irrational marketplace by inserting Meaning or Purpose (ethical principles) to attract ethical economic players who act to counterbalance centralized productive power. OSE's assumption is that if a particular economic route is beneficial to the largest number of people and environmentally sound, under the further ssumption of free enterprise – then it becomes the dominant form of enterprise.
Ethical Economy Definition
Background R&D Process
- Propose backround Briefing, based on Wikipedia and basic internet search.
- Search literature. Includes patents, scholarly articles, books. How to do a Literature Search.
- Identify world leading experts, and contact them. Contact them strategically.
- Submit OSE Requirement to the experts, soliciting feedback on a proposed pathway.
- If SME is willing, contract them for development work.
- Note: this template should be updated to reflect Zachman framework of different collaboraborator views. For example - add Zachman framework for Legal- Standards/Codes/Legal/Regulatory/Compliance/ view.
- Add Email Signature / License to Legal.
- Add to Legal View - Open standards - collaborate with Respects Your Freedom, OSHWA certified, free cultural works, etc
- Add OSHW Shitlist to Communications View
- Need to refactor this into current version via Zachman Framework - https://docs.google.com/spreadsheet/ccc?key=0Av4ZjQn4DHJHdEZJT0dMTktQT3ljUnFrT0NENEZVUGc#gid=2
These are possible layers of the OSE Zachman ontology:
- User - someone who reads our material like Wikipedia, or who builds GVCS machines
- Legal Layer
- Media Package viewpoint - for media to take our press releases and other assets
- Art Show viewpoint - for art shows/ exhibits to use our materials freely
- Community Building
- Product Development:
- Research & Background
- Extreme Manufacturing Optimization
- Enterprise (Distributive)
- Viral Replicability Criteria
- Humanism, Psychology, Meaning, Peak Performance
- Motivation within the big picture
- Systems Design
- State of the world and relationship to material production
- GVCS Product Ecologies
- Relationship to Other Projects