Project Development Template: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| (6 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
This build on former work at the [[GVCS_Development_Template]] | This build on former work at the | ||
*[[GVCS_Development_Template]] | |||
*[[Development Strategy]] | |||
and blog posts from | |||
*[http://blog.opensourceecology.org/2009/03/open-source-development-pipeline-continues-the-flow/ March 2009] | |||
*[http://blog.opensourceecology.org/2009/03/open-source-product-development-pipeline-refined/ May 2009] | |||
*[http://blog.opensourceecology.org/2010/07/open-product-development-pipeline/ July 2010], | |||
The latest iteration of the development method is summarized in the roles of the [[Projects Director]] | |||
* | |||
=Main Steps of Project Development= | |||
Our experience has shown this procedure to be effective in product development. | |||
#'''Product Specification and Design Rationale''' - also called '''Specification''' - see [[Specifications Specification]]. Clarity on this point is crucial, as this is a translation of [[OSE Specifications]] into an actual product design. This is the conversion of high level OSE Specification into specific design parameters. This specification needs to be sufficiently specific to allow any designer to create a full physical design. The mark of a successful Specification is that it is degenerate - 2 different developers in remote corners of the world would come up with a similar design. | |||
# | |||
[[Category:Recruiting]] | |||
[[Category:Standards]] | |||
Latest revision as of 22:51, 18 February 2012
This build on former work at the
and blog posts from
The latest iteration of the development method is summarized in the roles of the Projects Director
Main Steps of Project Development
Our experience has shown this procedure to be effective in product development.
- Product Specification and Design Rationale - also called Specification - see Specifications Specification. Clarity on this point is crucial, as this is a translation of OSE Specifications into an actual product design. This is the conversion of high level OSE Specification into specific design parameters. This specification needs to be sufficiently specific to allow any designer to create a full physical design. The mark of a successful Specification is that it is degenerate - 2 different developers in remote corners of the world would come up with a similar design.