๐ Task Creation Guidelines โ Advanced Analytics
Purpose
Tasks represent the individual units of work required to complete a Story. They break down the Story into actionable steps that can be completed within a day.
Ownership
- Tasks are created by the Story owner.
- All Tasks should be defined by the start of the sprint in which the Story is assigned.
- Tasks can be delegated to other team members or stakeholders as needed.
Scope & Granularity
- Each Task should be scoped to a single day of work.
- Tasks must be specific and actionable, contributing directly to the completion of the parent Story.
Linkage
- Every Task must have a parent link to a Story.
- Tasks should not exist independently outside of a Story.
Status Tracking
| Status | Description |
|---|---|
| New | Work hasn’t started. |
| Active | Work is in progress. |
| Closed | Task is complete. |
| Removed | Task is no longer relevant or has been replaced. |
Effort Tracking
- Once the Story is completed, the actual number of hours spent on each Task should be entered in the “Completed” field.
- If a user wants to track remaining work, they can enter the estimated hours left in the “Remaining” field under Work Details.