3.1.2. Task

Task

In AgileTrack, an issue is intended to be categorized as a task if it is an issues which doesn't represent a feature of a product, nor a defect. For example, "Configure a automated build environment" would be a likely title of a task as it is necessary work, though not tied directly to a product feature. Task records may be used at a user's discretion. Extreme Programming would suggest that such tasks would always be related to a user story.

Stories, tasks, and defects in AgileTrack may also all have sub-tasks defined. A sub-task is a task record which is tied to a particular parent task. In an Extreme Programming environment, sub-tasks would make up the implementation details of a story. In AgileTrack, sub-tasks have a few additional configurable behavior properties related to iteration planning, and classification.

Next Section: 3.1.3. Defect