XM Control Panel Howto

Introduction to Getting Involved

Welcome to the Control Panel for Open Product Development by Open Source Ecology. We are developing the Global Village Construction Set + the organizational framework which allows for the scaling of open source product development towards significant economic impact.

The goal of this HOWTO is to explain:

• New Contributors: Getting Involved. How a person who knows little about the project can get involved
  • Explain insights into how the Project Page can leverage extensive global collaboration - whether contributor works on a one-time or extended basis.
• New Project Managers (Scrum Masters and Product Owners): Getting Involved

New Contributors: Getting Involved

This is a platform for Open Source Product Development that intends to leverage small and large development contributions on any of a large number of development steps required to bring a physical product from idea to reality.

Volunteers and paid people are working on the project. For all new contributors:

The prerequisite to joining a team is performing a task on the Task Board.

To begin, examine the ~100 steps of the Control Panel. Click on the hyperlink to each step to examine what each step entails. Then go to the Task Board, and add a task that you would like to do. Either create a task in the To Do column, or take an existing task - sign it and move it into the In Progress column. If you create the task, contact the team to let us know what you are doing. When you are done, place it in the Verify column and email the Team contact requesting verification. If your work is approved - you have made it on the team. You will remain on the team as long as you complete at least one task per month. Joining the team includes being listed on the Team window and gaining access to edit the Status Log and Control Panel with your work product.

If you would like to be involved as an independent contractor for pay, please discuss this with the Scrum Master. Prior to doing so, please propose a bid as discussed under Bidding Process in the Masterlist of Steps.

Scrum Masters

Scrum Masters (SM) are the managers who take initiative to ensure that all the 87 steps of the development process occur, and that results are documented in a fashion which allows complete transparency - to facilitate involvement of others and project scaling. Scrum Masters:

• SM reports to PO and is accountable to team and global community via frequent publishing; accountable to 1B people in poverty
• The Tracker and Unblocker - Effective proficiency in project management and resource (human, material, other) development allocation
• Work with PO - where PO sets clear direction and informs SM as to what resources to bring in.
• Build the team - both on-site, off-site, and advisory capacities
• Focus on bringing the necessary resources (expertise, work force, materials) into the project to complete the 87 steps
• Invite external developmetn input
• Assure that proper review is ongoing, both on-site and off-site
• Organize Flash Mobs for helping with the project
• Develop access and rapport with off-site advisors and SMEs for on-call access to solving development issues.
• Are trained by the Stakeholder in the OSE Scrum Process, and in basics of OSE Open Product Development

Product Owners

Product Owners (PO) have a clear vision of the desired product. They perform development work, and when they are not doing developmetn, they are working with the Scrum Master to inform the effort of gathering resources.

• Essentially - a Director and COO for a project, inform the SM, reports to Stakeholder
• The PO takes on 2-6 products and runs forward with a clear
• Train by Stakeholder to have a crystal clear view of OSE Spec and exactly how it applies to the manifestation of the real product
• SM gophers for PO, and crowdsources answers from community, advisors, SMEs, Flash Mobs

Moving Forward...

Wa are forming the process, and learning rapidly from results. Immediately: need Project Platform for CNC Circuit Mill, Car, Ironworker. Then as we get more Scrum Masters, do: Gasifier, Torch Table, Backhoe, Sawmill, Steam Engine.

To start, need to identify Scrum Masters, Product Owner.

Next: training materials.

Framework of Development

Process

The Control Panel assumes that there is a framework of a Scrum Master and a Product Owner who 'run' the development process of the Global Village Construction Set. The assumption is further that there is an organization - OSE - providing funding for this development. Further, the organization is responsible for recruiting Advisers and Subject Matter Experts who can enhance the velocity greatly.

The Scrum Master is key in accelerating the process:

• Scrum Master works both locally (Factor e Farm) and Globally (remote collaboration and remote swarming (Flash Mobs))
• World can view and join at any time. By assuring that ALL the steps are documented, anyone in the world can begin contributing.
  • Buzz is generated when updates are constant.
• Task done on backlog qualifies a person to join a team.
• Person joining team qualifies to vlog and log tasks in completion log
• Flash Mobs are engaged for swarming on problems
• Advanced techniques such as 3D scans are generated to produce rapid CAD design
• CAD and Design can be done rapidly via remote swarms
• Prototyping work can be done rapidly at Factor e Farm with 12 Fabricators + 12 Assistants
• Remote fabrication can happen at TechShop or Home Machine Shop
• Rapid Fabrication and Design can be leveraged
  • Requires CAD swarm and design swarm - first focuses on documentation, other focuses on design - 1 hour per week.
• Rapid Prototyping/Testing can be leveraged
  • CAE swarming, 3D print swarming (For rapid prototypes), High School fab shops, Makerspaces

Platform Design Rationale

• Platform does not use links within the entries for the Master List of Steps. This is to facilitate navigation by preventing people from being taken away from the overall Project Page. Rate
• Tags (Categories) should be added to pages in the Mediawiki platform, such that any Master List of Steps item should be tagged by that name (such as this page is tagged XM Control Panel Howto at the bottom of this page.
  • The usefulness of this lies in examining a whole bunch of Steps from different machines to assess documentation standards and learn best practices from the other 50 GVCS projects.

Minimum Management Required:

• 12 fabricators at factor e farm (2 currently)
• 1 FeF documenter + upload strategy
• 10 scrum masters, 10 project owners
  • Needs weekly on-demand housing
• COO (manages Scrum)
• CEO (manages Project)
• CFO (Aaron)

Budget - $64k/month in management (32 people at $2k stipend, halp at Factor e Farm + half remote, then 25 on-site by Quarter 4)

Capacity

We can currently house a max of 15 people. Camping space is unlimited.

Volunteers Required:

• crowd-source documentation talent in the summer (film and journalism schools),
• Flash Design, CAD, CAE via volunteer engineers in Flash Mobs, supported via nonprofit sector; work with EWB
• Flash CAD via Sketchup to CAD conversion
• 1 mechanic for machine testing
• Crowdsource CAD from nonprofit
• Scaling Calculation Flash Mobs

Strategy

• Due Diligence via Scrum Master and Product Owner who are guided by an Advisory Board of Titans (100-200 advisors)
  • Mine via TED, EWB, LifeBoat, OSE True Fans + Supporters, Professional Headhunter, and others.
• Recruit full-time community manager for Flash Mob talent.
  • Flash Mob Brief - from Due Diligence
  • 1.5 hour design session on Google Hangout.

Category Nomenclature

• Clearly defined and differentiated terms should be used consistently within category names.

• Clear definitions need not be specific; definition-related redundancy can be minimized by categorizing certain terms under more general terms.

• Examples of terms up for consistent usage are:

• • "Strategy" is an explanation on how to do something.

• • "Analysis" is an explanation on what and how something is.

• • "Brief" is a summary of something.

• • "Testing" is a report on the results of experiments.