Development Task Durations: Difference between revisions
(Created page with "=Introduction= In order to quantify the process duration of the entire Development Process for open products - it is useful to document the time that every one of the ~100 dev...") |
No edit summary |
||
| Line 1: | Line 1: | ||
=Introduction= | =Introduction= | ||
In order to quantify the process duration of the entire Development Process for open products - it is useful to document the time that every one of the ~100 development tasks takes. To do this - please use this spreadsheet below to document any single task. Accurate evaluation of time can be obtaining by measurig several data points for each task - so that a range of times can be determined - based on different people, product complexities, product scopes, blocks, access to tools, and other conditions. This way, a mean value for the duration can be obtained as a general guideline for predicting delivery schedules. Lower and upper estimates of time can be determined for the development process, and the development process can be resource-loaded accordingly to provide predictable delivery of results. | In order to quantify the process duration of the entire Development Process for open products - it is useful to document the time that every one of the ~100 development tasks takes. To do this - please use this spreadsheet below to document any single task. Accurate evaluation of time can be obtaining by measurig several data points for each task - so that a range of times can be determined - based on different people, product complexities, product scopes, blocks, access to tools, and other conditions. This way, a mean value for the duration can be obtained as a general guideline for predicting delivery schedules. Lower and upper estimates of time can be determined for the development process, and the development process can be resource-loaded accordingly to provide predictable delivery of results. | ||
=Task Durations= | |||
<html>https://docs.google.com/spreadsheet/pub?key=0ArpE5Y9PpJCXdFpVZE4ySmIwaVM1VDdVdGtjbzJhWlE&output=html</html> | |||
[https://docs.google.com/a/opensourceecology.org/spreadsheet/ccc?key=0ArpE5Y9PpJCXdFpVZE4ySmIwaVM1VDdVdGtjbzJhWlE#gid=0 edit] | |||
Revision as of 13:34, 15 August 2013
Introduction
In order to quantify the process duration of the entire Development Process for open products - it is useful to document the time that every one of the ~100 development tasks takes. To do this - please use this spreadsheet below to document any single task. Accurate evaluation of time can be obtaining by measurig several data points for each task - so that a range of times can be determined - based on different people, product complexities, product scopes, blocks, access to tools, and other conditions. This way, a mean value for the duration can be obtained as a general guideline for predicting delivery schedules. Lower and upper estimates of time can be determined for the development process, and the development process can be resource-loaded accordingly to provide predictable delivery of results.
Task Durations
https://docs.google.com/spreadsheet/pub?key=0ArpE5Y9PpJCXdFpVZE4ySmIwaVM1VDdVdGtjbzJhWlE&output=html