GVCS Methodology: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
No edit summary
Line 1: Line 1:
== Introduction ==
== Introduction ==


This page is about the modular GVCS methodology (mGm).   
This page is about the modular[http://www.example.com link title] GVCS methodology (mGm).   


Using the [[The Lean Startup Process]] approach of no waste and no duplication of efforts, and applying the [[scrum]] process of prioritization, progress visualization, and rapid deployment, this systematic approach will mitigate the risks(cost, performance, schedule) and ensure the development and delivery of the GVCS. It will also help with the [[scalability]] and parallel development of the GVCS by encouraging cross-collaboration between projects within the GVCS-50.
Using the [[The Lean Startup Process]] approach of no waste and no duplication of efforts, and applying the [[scrum]] process of prioritization, progress visualization, and rapid deployment, this systematic approach will mitigate the risks(cost, performance, schedule) and ensure the development and delivery of the GVCS. It will also help with the [[scalability]] and parallel development of the GVCS by encouraging cross-collaboration between projects within the GVCS-50.


== The Methodology ==
== The Methodology ==

Revision as of 10:57, 23 February 2012

Introduction

This page is about the modularlink title GVCS methodology (mGm).

Using the The Lean Startup Process approach of no waste and no duplication of efforts, and applying the scrum process of prioritization, progress visualization, and rapid deployment, this systematic approach will mitigate the risks(cost, performance, schedule) and ensure the development and delivery of the GVCS. It will also help with the scalability and parallel development of the GVCS by encouraging cross-collaboration between projects within the GVCS-50.

The Methodology

Scrumiteration.jpg

The key to rapid deployment(billions have been wasted to figure this one secret factor)... drum roll.... collaboration. Yup, like ice ice baby.

1. Gather requirements 2. Design the solution(s) 3. Build the solution 4. Test the solution 5. Iterate

Build a little, test a little, fail a little, learn a lot.

[1]

Use Cases

Proven projects from government, industry and academia that are extremely successful(not just in terms of money, but contribution to the world) using the scrum approach.

[2] The WIKISPEED 100+ MPG car.


mGm certified

Do not let the fancy word of certification scares you. This is a place where various project leads can show off how awesome their projects are because they either reduced waste or simply is on track with production.

Education

Better yourself. The lean approach can also be applied to your life, not just manufacturing or production. Read more about how the lean approach is extremely Zen-like. Please share your knowledge here so others can be lean too.

[3]