Development Process Transparency: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 13: | Line 13: | ||
*project funding being voted with the wallets of funders, and the [[GVCS Development Priorities]] for any blank votes | *project funding being voted with the wallets of funders, and the [[GVCS Development Priorities]] for any blank votes | ||
For the last point, it may be instructive to develop an explicit voting page. Any donor has the opportunity to vote on a project. A project will be begun upon the necessary [[Development Prerequisites]] being met according to the [[GVCS Development Template]]. | For the last point, it may be instructive to develop an explicit voting page. Any donor has the opportunity to vote on a project. A project will be begun upon the necessary [[GVCS Product Development Prerequisites]] being met according to the [[GVCS Development Template]]. | ||
Revision as of 09:34, 17 February 2011
GVCS Development Process Transparency involves documentation of:
- clarity on the goals
- the identity, skill base, and commitments of the team
- the development process procedures
- evaluation procedures
- decision-making processes
For technical GVCS development, this is satisfied, respectively, by:
- following the 50/2/2 goal
- participants filling out the Team Culturing survey
- following the Web Collaboration Strategy
- adhering to OSE Specifications and calculating an OSE Specifications Score; evaluating Bid Proposals with the Technical Review Team
- project funding being voted with the wallets of funders, and the GVCS Development Priorities for any blank votes
For the last point, it may be instructive to develop an explicit voting page. Any donor has the opportunity to vote on a project. A project will be begun upon the necessary GVCS Product Development Prerequisites being met according to the GVCS Development Template.