Development Task Durations: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
(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...")
 
 
(4 intermediate revisions by the same user not shown)
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 (see [[Product Development Master Template]]) - 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><iframe width=100% height='500' frameborder='0' src='https://docs.google.com/spreadsheet/pub?key=0ArpE5Y9PpJCXdFpVZE4ySmIwaVM1VDdVdGtjbzJhWlE&output=html&widget=true'></iframe></html>
 
[https://docs.google.com/a/opensourceecology.org/spreadsheet/ccc?key=0ArpE5Y9PpJCXdFpVZE4ySmIwaVM1VDdVdGtjbzJhWlE#gid=0 edit]

Latest revision as of 13:50, 15 August 2013

Introduction

In order to quantify the process duration of the entire development process for open products (see Product Development Master Template) - 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

edit