Difference between revisions of "Progress Tracking"

Revision as of 21:02, 3 June 2014

Task Types - High, Medium, and Low-Level

Tracking the progress of hierarchical nested tasks need to address different problems on different task abstraction levels. A task on the root level can take a long time and has probably a high abstraction. E.g. “The Age of Water” task in this wiki. Tasks on the leaf level can be characterized by low abstraction and shorter duration. Therefor we decide to introduce three different task types Low-Level, Medium-Level and High-Level tasks. The type prefix describes the level of abstraction that means a Low-Level task has a low abstraction. Every type has a different color, on Low-Level task the degree of abstraction is low and the progress estimation is exact this is expressed with the dark green color. Light green represents the High-Level tasks with lower progress estimation accuracy. Low-Level tasks are tracked in percentage directly by asking the task leader. Medium-Level tasks are intermediate tasks in between high and low level tasks.

Automatic Estimation of Progress

The progress is tracked by aggregating the progress of all related subtasks.

The progress tracking is based on the structured properties described in the task representation and timeline tracking. To ensure a preferably accurate measurement which represents the current state of a High-Level task, the progress calculation is based on start and target date. Our assumption is that after half of the task duration, the expected task progress would be 50 percent.

Failed to parse (Missing <code>texvc</code> executable. Please see math/README to configure.): \tiny{Start date: 04/16/2014}
Failed to parse (Missing <code>texvc</code> executable. Please see math/README to configure.): Today's date: 06/16/2014
Failed to parse (Missing <code>texvc</code> executable. Please see math/README to configure.): Target date: 08/16/2014
Failed to parse (Missing <code>texvc</code> executable. Please see math/README to configure.): /frac{TodaysDate-StartDate}{TargetDate-StartDate} = /frac{}{}

In case we would use the aggregation method as described for the medium level tasks the estimation would be far inaccurate. The aggregation concept is optimal when most of the subtasks are known at the tasks start date. In reality especially high level tasks will emerge during the time. E.g. one subtask is known at the start of a high level task and more subtasks are added during the time. In an early task state the progress would be much too high due to the fact that the later added subtasks not considered by the progress calculation via aggregation. High level tasks are probably uses most on root level tasks but depending on the degree of abstraction within the tasks hierarchy high level task can be used in lower hierarchy levels.

I think the above needs to be explained better -- Yolanda

"%" is not declared as a valid unit of measurement for this property.