OSE Wikispeed Development Procedure
<html><head><title>Extreme Manufacturing</title><style type="text/css">ol{margin:0;padding:0}p{margin:0}.c1{list-style-type:decimal;margin:0;padding:0}.c2{font-size:10pt;background-color:#ffffff;font-weight:bold}.c8{max-width:468pt;background-color:#ffffff;padding:72pt 72pt 72pt 72pt}.c6{padding-left:0pt;direction:ltr;margin-left:53pt}.c7{height:11pt;direction:ltr}.c0{color:inherit;text-decoration:inherit}.c10{color:#1155cc;text-decoration:underline}.c3{font-size:10pt;background-color:#ffffff}.c9{font-style:italic}.c11{direction:ltr}.c4{color:#5a3696}.c5{color:#a55858}.title{padding-top:24pt;line-height:1.15;text-align:left;color:#000000;font-size:36pt;font-family:Arial;font-weight:bold;padding-bottom:6pt}.subtitle{padding-top:18pt;line-height:1.15;text-align:left;color:#666666;font-style:italic;font-size:24pt;font-family:Georgia;padding-bottom:4pt}body{color:#000000;font-size:11pt;font-family:Arial}h1{padding-top:24pt;line-height:1.15;text-align:left;color:#000000;font-size:18pt;font-family:Arial;font-weight:bold;padding-bottom:6pt}h2{padding-top:18pt;line-height:1.15;text-align:left;color:#000000;font-size:14pt;font-family:Arial;font-weight:bold;padding-bottom:4pt}h3{padding-top:14pt;line-height:1.15;text-align:left;color:#666666;font-size:12pt;font-family:Arial;font-weight:bold;padding-bottom:4pt}h4{padding-top:12pt;line-height:1.15;text-align:left;color:#666666;font-style:italic;font-size:11pt;font-family:Arial;padding-bottom:2pt}h5{padding-top:11pt;line-height:1.15;text-align:left;color:#666666;font-size:10pt;font-family:Arial;font-weight:bold;padding-bottom:2pt}h6{padding-top:10pt;line-height:1.15;text-align:left;color:#666666;font-style:italic;font-size:10pt;font-family:Arial;padding-bottom:2pt}</style></head><body class="c8">
This is a procedure applied to each product of the GVCS. This is intended to become a generalized platform for open source product development. Stakeholder is an individual, and an Organization (OSE) develops a greater network of Funders, Subject Matter Experts, Review Teams, Advisory Boards, Communications, Extreme Manufacturing Platform, etc.
- Stake Holder Defines Goals for Product - Strategy: moonshot thinking for sound design. Work Product: one sentence or paragraph defining the product at the broadest level posted on the wiki, with wiki page dated for currency. Stake Holder maintains a list of Goals and Product OwnersEx. I want a car that gets 100 mpg that is also integrated into the overall product ecology of the GVCS, such as power cube interchangeability, gasifier burner, pelletized biomass fuel.
- Stake Holder Identifies and Recruits Product Owner (person with clear, but evolvable, vision) - Work Product: <a class="c0" href="http://opensourceecology.org/w/index.php?title=Subject_Matter_Expert_Contract&action=edit&redlink=1">Subject Matter Expert Contract</a>(defining responsibilities) written with assistance of <a class="c0" href="http://opensourceecology.org/wiki/Shuttleworth_Foundation">Shuttleworth Foundation</a>, posted on the wiki, dated. Open IP/Distributive Enterprise clause agreed upon. Checklist is part of contract - <a class="c0" href="http://opensourceecology.org/w/index.php?title=Subject_Matter_Expert_Checklist&action=edit&redlink=1">Subject Matter Expert Checklist</a> - defining all aspects of relationship including SME qualifications and contact info, assessment of Open Culture embodied by SME, etc.
- Product Owner Recruits Scrum Master - or Process Coach. Work Product: <a class="c0" href="http://opensourceecology.org/wiki/Scrum_Master_Contract">Scrum Master Contract</a> (defining responsibilities) written with assistance of <a class="c0" href="http://opensourceecology.org/wiki/Shuttleworth_Foundation">Shuttleworth Foundation</a>, posted on the wiki, dated. Open IP/Distributive Enterprise clause agreed upon. Backlog is part of contract - <a class="c0" href="http://opensourceecology.org/w/index.php?title=Project_Deliverables_Checklist&action=edit&redlink=1">Project Deliverables Checklist</a> - defining all user stories required to deliver initial Stake Holder goals.
- Scrum Master recruits Project Team - Work Product: team members published on wiki, with photograph, intro video with hours of commitment, contracts. Smart phone rapid vlogging and open IP policy established with team. Checklist -<a class="c0" href="http://opensourceecology.org/wiki/OSE_Wikispeed_Development_Team_Requirements">OSE Wikispeed Development Team Requirements.</a>
- Product Owner Defines Product Specifications + Design Rationale - Work Product: written specification + design rationale posted as a separate page on the wiki, dated.
- Scrum Master deploys team and documents all results on wiki - Scrum Master (SM) maintains list of and recruits further members for <a class="c0" href="http://opensourceecology.org/wiki/Extreme_Manufacturing_Subject_Matter_Expert_Team">Extreme Manufacturing Subject Matter Expert Team</a>. SM instigates progress and Reviews. Project Team produces results and vlogs, SM documents and organizes all of this on Wiki and in <a class="c0" href="http://opensourceecology.org/wiki/Connexions">Connexions</a> platform. SM submits reviewed Budget to Stake Holder. Communicates with Stakeholder on any blocks. Instigates Swarming within Project Team or with other project SMs.
</body></html>