Development Velocity: Difference between revisions
No edit summary |
No edit summary |
||
| 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]]. | ||
Revision as of 14:19, 9 February 2017
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 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.