subtasks

Subtasks are smaller tasks derived from a larger task, used to break work into manageable pieces. They appear in project management, software development, and workflow systems to help planning, assignment, and tracking. They often form a hierarchical structure with a parent task and one or more subtasks.

A subtask inherits context from the parent task (scope, overall objective) but typically has its own attributes such as assignee, due date, estimates, and status. Subtasks can be independent or dependent on other subtasks; some tools model dependencies so that a subtask cannot start until its predecessors are complete.

In practice, subtasks support planning and execution by enabling parallel work, enabling finer-grained estimates, and providing progress signals. They are useful for teams that require clear ownership and progress breakdown within larger features or initiatives. Example: under a feature task "Implement user authentication," subtasks might include "Design login flow," "Implement backend API," "Create UI," and "Write tests."

Best practices: define clear completion criteria for each subtask, avoid excessive depth, keep naming consistent, and ensure alignment with the parent task. Use time estimates and due dates carefully to prevent over- or under- planning; regularly review subtasks to avoid drift.

Limitations: subtasks add management overhead and can obscure the bigger picture if overused. They require explicit dependencies and up-to-date status. Tools and teams should balance granularity with maintainability.