Development Velocity - Revision history

Marcin at 14:38, 9 February 2017

2017-02-09T14:38:07Z

← Older revision		Revision as of 14:38, 9 February 2017
Line 3:		Line 3:
	For a complete development project starting from zero to a fully documented prototype - the time should be 1 person day per [[Development Template]] item, of which there are about 40 for the first page of the Development Template. This does not include Distributive Enterprise or any other assets from the [[Zachman Framework]] viewpoints. Thus, it should take 40 days for project completion per module. A typical hardware has 12 modules, therefore the development time should total 480 days per project, or 1.3 human years.		For a complete development project starting from zero to a fully documented prototype - the time should be 1 person day per [[Development Template]] item, of which there are about 40 for the first page of the Development Template. This does not include Distributive Enterprise or any other assets from the [[Zachman Framework]] viewpoints. Thus, it should take 40 days for project completion per module. A typical hardware has 12 modules, therefore the development time should total 480 days per project, or 1.3 human years.

	About 1 year of development is a reasonable number - and of course that number depends on product quality. Perhaps it could be said that it takes 1.3 years for a Version 1 or a [[Minimum Viable Product]]. Quality can improve indefinitely, even if [[Viral Replicability Criteria]] are reached. That does not mean that new features are introduced. In fact, successive iterations may take features out - by the principle of Sufficiency embodied in point 29 of the [[OSE Specifications]].		About 1 year of [[Skunkworks]] development is a reasonable number - and of course that number depends on product quality. Perhaps it could be said that it takes 1.3 years for a Version 1 or a [[Minimum Viable Product]]. Quality can improve indefinitely, even if [[Viral Replicability Criteria]] are reached. That does not mean that new features are introduced. In fact, successive iterations may take features out - by the principle of Sufficiency embodied in point 29 of the [[OSE Specifications]].

	The important concept to note is that of ~~Velocity Increase~~ for Development Time Compression. If it takes about 1 year (365 human days) to complete a project, then to compress a development cycle to 1 week would require roughly 50 people to work at the same time.		The important concept to note is that of ''velocity increase'' for [[Development Time Compression]]. If it takes about 1 year (365 human days) to complete a project, then to compress a development cycle to 1 week would require roughly 50 people to work at the same time.

	OSE's goals are to demonstrate optimum Development Time Compression via task parallelization, as in [[Concurrent Engineering]].		OSE's goals are to demonstrate optimum Development Time Compression via task parallelization, as in [[Concurrent Engineering]].

Marcin at 14:25, 9 February 2017

2017-02-09T14:25:15Z

← Older revision		Revision as of 14:25, 9 February 2017
Line 3:		Line 3:
	For a complete development project starting from zero to a fully documented prototype - the time should be 1 person day per [[Development Template]] item, of which there are about 40 for the first page of the Development Template. This does not include Distributive Enterprise or any other assets from the [[Zachman Framework]] viewpoints. Thus, it should take 40 days for project completion per module. A typical hardware has 12 modules, therefore the development time should total 480 days per project, or 1.3 human years.		For a complete development project starting from zero to a fully documented prototype - the time should be 1 person day per [[Development Template]] item, of which there are about 40 for the first page of the Development Template. This does not include Distributive Enterprise or any other assets from the [[Zachman Framework]] viewpoints. Thus, it should take 40 days for project completion per module. A typical hardware has 12 modules, therefore the development time should total 480 days per project, or 1.3 human years.

	1~~.3 years~~ is a ~~decent~~ number - and of course that number depends on product quality. Perhaps it could be said that it takes 1.3 years for a Version 1 or a [[Minimum Viable Product]]. Quality can improve indefinitely, even if [[Viral Replicability Criteria]] are reached. That does not mean that new features are introduced. In fact, successive iterations may take features out - by the principle of Sufficiency embodied in point 29 of the [[OSE Specifications]].		About 1 year of development is a reasonable number - and of course that number depends on product quality. Perhaps it could be said that it takes 1.3 years for a Version 1 or a [[Minimum Viable Product]]. Quality can improve indefinitely, even if [[Viral Replicability Criteria]] are reached. That does not mean that new features are introduced. In fact, successive iterations may take features out - by the principle of Sufficiency embodied in point 29 of the [[OSE Specifications]].

			The important concept to note is that of Velocity Increase for Development Time Compression. If it takes about 1 year (365 human days) to complete a project, then to compress a development cycle to 1 week would require roughly 50 people to work at the same time.

			OSE's goals are to demonstrate optimum Development Time Compression via task parallelization, as in [[Concurrent Engineering]].

Marcin at 14:19, 9 February 2017

2017-02-09T14:19:12Z

← Older revision		Revision as of 14:19, 9 February 2017
Line 3:		Line 3:
	For a complete development project starting from zero to a fully documented prototype - the time should be 1 person day per [[Development Template]] item, of which there are about 40 for the first page of the Development Template. This does not include Distributive Enterprise or any other assets from the [[Zachman Framework]] viewpoints. Thus, it should take 40 days for project completion per module. A typical hardware has 12 modules, therefore the development time should total 480 days per project, or 1.3 human years.		For a complete development project starting from zero to a fully documented prototype - the time should be 1 person day per [[Development Template]] item, of which there are about 40 for the first page of the Development Template. This does not include Distributive Enterprise or any other assets from the [[Zachman Framework]] viewpoints. Thus, it should take 40 days for project completion per module. A typical hardware has 12 modules, therefore the development time should total 480 days per project, or 1.3 human years.

	1.3 years is a decent number - and of course that number depends on product quality. Perhaps it could be said that it takes 1.3 years for a Version 1 or a [[Minimum Viable Product]]. Quality can improve indefinitely, even if [[Viral Replicability Criteria]] are reached. That does not mean that new features are introduced. In fact, successive iterations may take features out - by the principle of Sufficiency embodied in [[OSE Specifications]].		1.3 years is a decent number - and of course that number depends on product quality. Perhaps it could be said that it takes 1.3 years for a Version 1 or a [[Minimum Viable Product]]. Quality can improve indefinitely, even if [[Viral Replicability Criteria]] are reached. That does not mean that new features are introduced. In fact, successive iterations may take features out - by the principle of Sufficiency embodied in point 29 of the [[OSE Specifications]].

Marcin at 14:18, 9 February 2017

2017-02-09T14:18:31Z

← Older revision		Revision as of 14:18, 9 February 2017
Line 3:		Line 3:
	For a complete development project starting from zero to a fully documented prototype - the time should be 1 person day per [[Development Template]] item, of which there are about 40 for the first page of the Development Template. This does not include Distributive Enterprise or any other assets from the [[Zachman Framework]] viewpoints. Thus, it should take 40 days for project completion per module. A typical hardware has 12 modules, therefore the development time should total 480 days per project, or 1.3 human years.		For a complete development project starting from zero to a fully documented prototype - the time should be 1 person day per [[Development Template]] item, of which there are about 40 for the first page of the Development Template. This does not include Distributive Enterprise or any other assets from the [[Zachman Framework]] viewpoints. Thus, it should take 40 days for project completion per module. A typical hardware has 12 modules, therefore the development time should total 480 days per project, or 1.3 human years.

	1.3 years is a decent number - and of course that number depends on product quality. Perhaps it could be said that it takes 1.3 years for a Version 1 of a ~~product - but a product~~ can improve indefinitely~~. This is true~~ even if a [[~~Minimum Viable Product~~]] is reached.		1.3 years is a decent number - and of course that number depends on product quality. Perhaps it could be said that it takes 1.3 years for a Version 1 or a [[Minimum Viable Product]]. Quality can improve indefinitely, even if [[Viral Replicability Criteria]] are reached. That does not mean that new features are introduced. In fact, successive iterations may take features out - by the principle of Sufficiency embodied in [[OSE Specifications]].

Marcin: Created page with "Development Velocity is the rate of burndown for a project. Velocity can be expressed, for example, as 30 days for project completion. For a complete development project star..."

2017-02-09T14:10:22Z

Created page with "Development Velocity is the rate of burndown for a project. Velocity can be expressed, for example, as 30 days for project completion. For a complete development project star..."

New page

Development Velocity is the rate of burndown for a project. Velocity can be expressed, for example, as 30 days for project completion.

For a complete development project starting from zero to a fully documented prototype - the time should be 1 person day per [[Development Template]] item, of which there are about 40 for the first page of the Development Template. This does not include Distributive Enterprise or any other assets from the [[Zachman Framework]] viewpoints. Thus, it should take 40 days for project completion per module. A typical hardware has 12 modules, therefore the development time should total 480 days per project, or 1.3 human years.

1.3 years is a decent number - and of course that number depends on product quality. Perhaps it could be said that it takes 1.3 years for a Version 1 of a product - but a product can improve indefinitely. This is true even if a [[Minimum Viable Product]] is reached.