OSE Wikispeed Development Procedure: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
#'''Product Owner Defines Vision or Story 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. | #'''Product Owner Defines Vision or Story 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. | ||
#''' | #'''Product Owner Identifies and Recruits Subject Matter Expert''' - Work Product: [[Subject Matter Expert Contract]] (defining responsibilities) written with assistance of [[Shuttleworth Foundation]], posted on the wiki, dated. Open IP/Distributive Enterprise clause agreed upon. Checklist is part of contract - [[Subject Matter Expert Checklist]] - 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 Project Director. Work Product: [[Scrum Master Contract]] (defining responsibilities) written with assistance of [[Shuttleworth Foundation]], posted on the wiki, dated. Open IP/Distributive Enterprise clause agreed upon. Checklist is part of contract - [[Project Deliverables Checklist]] - defining all deliverables required. | |||
#'''Scrum Master recruits delivery 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 - [[OSE Wikispeed Development Team Requirements]] | #'''Scrum Master recruits delivery 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 - [[OSE Wikispeed Development Team Requirements]] | ||
#'''Product Owner Defines Product Specifications + Design Rationale''' - Work Product: written specification + design rationale posted as a separate page on the wiki, dated. | #'''Product Owner Defines Product Specifications + Design Rationale''' - Work Product: written specification + design rationale posted as a separate page on the wiki, dated. | ||
Revision as of 04:49, 8 March 2012
This is a procedure applied to each product of the GVCS. This is intended to become a generalized platform for open source product development.
- Product Owner Defines Vision or Story 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.
- Product Owner Identifies and Recruits Subject Matter Expert - Work Product: Subject Matter Expert Contract (defining responsibilities) written with assistance of Shuttleworth Foundation, posted on the wiki, dated. Open IP/Distributive Enterprise clause agreed upon. Checklist is part of contract - Subject Matter Expert Checklist - 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 Project Director. Work Product: Scrum Master Contract (defining responsibilities) written with assistance of Shuttleworth Foundation, posted on the wiki, dated. Open IP/Distributive Enterprise clause agreed upon. Checklist is part of contract - Project Deliverables Checklist - defining all deliverables required.
- Scrum Master recruits delivery 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 - OSE Wikispeed Development Team Requirements
- Product Owner Defines Product Specifications + Design Rationale - Work Product: written specification + design rationale posted as a separate page on the wiki, dated.