OSE Project Phases - Revision history

Mjn: Redirected page to OSE Project Stages

2011-06-19T18:00:19Z

← Older revision		Revision as of 18:00, 19 June 2011
Line 1:		Line 1:
	[[~~Redirect:~~OSE Project Stages]]		#REDIRECT [[OSE Project Stages]]

Mjn at 17:59, 19 June 2011

2011-06-19T17:59:37Z

← Older revision		Revision as of 17:59, 19 June 2011
Line 1:		Line 1:
	[[~~Forward~~:OSE Project Stages]]		[[Redirect:OSE Project Stages]]

Mjn at 17:59, 19 June 2011

2011-06-19T17:59:21Z

← Older revision		Revision as of 17:59, 19 June 2011
Line 1:		Line 1:
	[[~~Redirected~~:OSE Project Stages]]		[[Forward:OSE Project Stages]]

Mjn: Replaced content with "Redirected:OSE Project Stages"

2011-06-19T17:58:53Z

Replaced content with "Redirected:OSE Project Stages"

← Older revision		Revision as of 17:58, 19 June 2011
Line 1:		Line 1:
			[[Redirected:OSE Project Stages]]
	Not all (in fact, most) OSE projects will be instantly spun-up into a mission-critical, fully staffed project. For this reason, OSE recognizes that projects can advance through several 'stages'. These are:

	~~# '''Idea''' - kicking around ideas, gathering data, etc.~~
	~~# '''Incubation''' - research, designs, initial plans, etc.~~
	~~# '''Development''' - build plans, CAD, CAM, prototyping, etc.~~
	~~# '''Support''' - a mature proven product focused on incremental improvements, support, marketing, etc.~~


	~~=OSE Idea Project=~~

	At the very earliest stage of an OSE project, one or more people come together with an idea for a new project. To be considered an OSE Idea Project, it should be aligned with the mission and goals of the Open Source Ecology project. It should contribute, in large part or small, to advancing our shared goals of creating the support technology and tools for OSE villages. It might be an idea central to energy or food production, it might be a project that contributes to one of the existing GVCS projects (like developing a open source stepper motor, for example), it might be a process improvement, etc.

	Regardless of scope, the idea phase is intended to allow information to be gathered, examined, and assessed for use in accomplishing the project goal. Collection of information should be done in the OSE wiki. Check first to see if anyone has already started up pages related to this idea. If so, it gives a good place to start from. If previous contributors are not part of your new idea project, contact them and invite them to participate - building a team is essential to the success of any OSE project.

	~~'''Idea Project Resources'''~~

	* Wiki Space - information on the idea project should be gathered and documented in the OSE wiki

	~~=OSE Incubated Project=~~

	At some point, the new OSE project becomes a serious development effort. Usually this happens when the focus of the project shifts from research and information gathering to design and early development. Projects many apply to the OSE Project Coordinator to become an incubated project. It is in the best interest of OSE and its members to establish new projects and requests for incubation status are likely to be granted, but projects must meet the following requirements:

	~~# A designated project leader~~
	~~# A team of two or more committed contributors~~
	~~# A project proposal in the wiki that describes the goals of this project~~
	~~# Background information, research, relevant links, etc. documented in the wiki.~~

	~~'''Incubated Project Resources'''~~

	* Wiki Space - product documentation is expected to start organizing wiki information according to OSE project and documentation standards.
	* Forum - on request, an OSE technical forum can be created to discuss topics related to this new project.
	* Pivotal - a project tracking space is created for the team to use for planning and tracking purposes.
	* GitHub - a document and software management system can be created on request to store key project documents and software (if any).


	=OSE ~~Development~~ Project=

	Eventually, the OSE project team will reach a point where prototyping and product development is ready to start. While experimental prototyping can be done during the incubation phase, implementation in the development phase is expected to be done according to OSE development standards. This means that parts are fully described and sourced. They are documented in 2D technical drawings and 3D CAD renders. Detailed build instructions are developed that explain parts fabrication or modification and instructions on product assembly is provided. As prototyping is conducted, it is documented with pictures and videos needed to create a final set of build instructions.

	Advancement to becoming an OSE Development Project is done through application to the OSE Project Coordinator, who will consult with the OSE Executive Director. With approval, the project becomes a full OSE project. While it may not be included in the GVCS list(depending on focus and other factors), it will be included in the larger list of established OSE projects. Advancement to the development phase requires:

	~~# A designated project manager~~
	~~# A established team of contributors~~
	~~# A detailed project proposal that includes system engineering breakdown, product ecology, and other documentation requirements.~~
	~~# A preliminary product design~~
	~~# A project development plan laid out in Pivotal~~

	~~'''Development Project Resources'''~~

	* Wiki Space - product documentation is expected to conform to OSE project and documentation standards.
	* Forum - on request, an OSE technical forum can be created to discuss topics related to this new project.
	* Pivotal - a project tracking space should be used by the team to coordinate project planning and tracking.
	* GitHub - should be used to store key project documents and software.
	* OSE Specialists - access to OSE development specialists such as CAD/CAM experts, ergonomic designers, fabrication experts, etc.
	* Funding Support - access to OSE funding sources and guidance in how to raise funds for project development.


	~~=OSE Support Project=~~

	After an unspecified amount of time, the OSE project transitions from being a development project to being a support project. This happens after the product moves into regular development in OSE fabrication facilities and starts to be built by external facilities, shops, and organizations. The focus becomes one of customer support, resolving problems, improving the quality of the documentation, developing "build kits", promoting the product at Maker Faires and similar events, etc.

	~~Support projects will have:~~

	~~# An established project manager~~
	~~# A customer support manager~~
	~~# An experienced support team~~
	~~# Solid assembly and fabrication documentation including photos and videos.~~
	~~# Proof of concept and successful implementation storis~~

	~~'''Support Project Resources'''~~

	* Wiki Space - product documentation is expected to conform to OSE project and documentation standards.
	* Forum - an OSE technical forum can be created to discuss topics related to this new project.
	* Pivotal - a project tracking space should be used by the team to coordinate project planning and tracking.
	* GitHub - should be used to store key project documents and software.
	* Bug Tracking - an issue management system should be used to track, resolve, and report product issues.

	~~[[Category:Standards~~]]

Mjn at 17:56, 19 June 2011

2011-06-19T17:56:43Z

← Older revision		Revision as of 17:56, 19 June 2011
Line 1:		Line 1:
	~~{{Category=Standards}}~~

	Not all (in fact, most) OSE projects will be instantly spun-up into a mission-critical, fully staffed project. For this reason, OSE recognizes that projects can advance through several 'stages'. These are:		Not all (in fact, most) OSE projects will be instantly spun-up into a mission-critical, fully staffed project. For this reason, OSE recognizes that projects can advance through several 'stages'. These are:

Mjn: Moved out of Starting an OSE Project.

2011-06-19T17:53:27Z

Moved out of Starting an OSE Project.

New page

{{Category=Standards}}

Not all (in fact, most) OSE projects will be instantly spun-up into a mission-critical, fully staffed project. For this reason, OSE recognizes that projects can advance through several 'stages'. These are:

# '''Idea''' - kicking around ideas, gathering data, etc.
# '''Incubation''' - research, designs, initial plans, etc.
# '''Development''' - build plans, CAD, CAM, prototyping, etc.
# '''Support''' - a mature proven product focused on incremental improvements, support, marketing, etc.

=OSE Idea Project=

At the very earliest stage of an OSE project, one or more people come together with an idea for a new project. To be considered an OSE Idea Project, it should be aligned with the mission and goals of the Open Source Ecology project. It should contribute, in large part or small, to advancing our shared goals of creating the support technology and tools for OSE villages. It might be an idea central to energy or food production, it might be a project that contributes to one of the existing GVCS projects (like developing a open source stepper motor, for example), it might be a process improvement, etc.

Regardless of scope, the idea phase is intended to allow information to be gathered, examined, and assessed for use in accomplishing the project goal. Collection of information should be done in the OSE wiki. Check first to see if anyone has already started up pages related to this idea. If so, it gives a good place to start from. If previous contributors are not part of your new idea project, contact them and invite them to participate - building a team is essential to the success of any OSE project.

'''Idea Project Resources'''

* Wiki Space - information on the idea project should be gathered and documented in the OSE wiki

=OSE Incubated Project=

At some point, the new OSE project becomes a serious development effort. Usually this happens when the focus of the project shifts from research and information gathering to design and early development. Projects many apply to the OSE Project Coordinator to become an incubated project. It is in the best interest of OSE and its members to establish new projects and requests for incubation status are likely to be granted, but projects must meet the following requirements:

# A designated project leader
# A team of two or more committed contributors
# A project proposal in the wiki that describes the goals of this project
# Background information, research, relevant links, etc. documented in the wiki.

'''Incubated Project Resources'''

* Wiki Space - product documentation is expected to start organizing wiki information according to OSE project and documentation standards.
* Forum - on request, an OSE technical forum can be created to discuss topics related to this new project.
* Pivotal - a project tracking space is created for the team to use for planning and tracking purposes.
* GitHub - a document and software management system can be created on request to store key project documents and software (if any).

=OSE Development Project=

Eventually, the OSE project team will reach a point where prototyping and product development is ready to start. While experimental prototyping can be done during the incubation phase, implementation in the development phase is expected to be done according to OSE development standards. This means that parts are fully described and sourced. They are documented in 2D technical drawings and 3D CAD renders. Detailed build instructions are developed that explain parts fabrication or modification and instructions on product assembly is provided. As prototyping is conducted, it is documented with pictures and videos needed to create a final set of build instructions.

Advancement to becoming an OSE Development Project is done through application to the OSE Project Coordinator, who will consult with the OSE Executive Director. With approval, the project becomes a full OSE project. While it may not be included in the GVCS list(depending on focus and other factors), it will be included in the larger list of established OSE projects. Advancement to the development phase requires:

# A designated project manager
# A established team of contributors
# A detailed project proposal that includes system engineering breakdown, product ecology, and other documentation requirements.
# A preliminary product design
# A project development plan laid out in Pivotal

'''Development Project Resources'''

* Wiki Space - product documentation is expected to conform to OSE project and documentation standards.
* Forum - on request, an OSE technical forum can be created to discuss topics related to this new project.
* Pivotal - a project tracking space should be used by the team to coordinate project planning and tracking.
* GitHub - should be used to store key project documents and software.
* OSE Specialists - access to OSE development specialists such as CAD/CAM experts, ergonomic designers, fabrication experts, etc.
* Funding Support - access to OSE funding sources and guidance in how to raise funds for project development.

=OSE Support Project=

After an unspecified amount of time, the OSE project transitions from being a development project to being a support project. This happens after the product moves into regular development in OSE fabrication facilities and starts to be built by external facilities, shops, and organizations. The focus becomes one of customer support, resolving problems, improving the quality of the documentation, developing "build kits", promoting the product at Maker Faires and similar events, etc.

Support projects will have:

# An established project manager
# A customer support manager
# An experienced support team
# Solid assembly and fabrication documentation including photos and videos.
# Proof of concept and successful implementation storis

'''Support Project Resources'''

* Wiki Space - product documentation is expected to conform to OSE project and documentation standards.
* Forum - an OSE technical forum can be created to discuss topics related to this new project.
* Pivotal - a project tracking space should be used by the team to coordinate project planning and tracking.
* GitHub - should be used to store key project documents and software.
* Bug Tracking - an issue management system should be used to track, resolve, and report product issues.

[[Category:Standards]]