Sub-tasks refer to a set of elements of a broader entity (parent task or sub-project) to define and describe an amount of work required to ensure success of this entity and accomplish its goals and objectives. These elements aim to create workflow compound that determines the simplest actions and operations necessary to deliver the parent task or sub-project.
Sub-tasks (aka "child tasks") are always interdependent on each other and aligned with goals and objectives of their parent entity. They can be visually displayed on a work flow diagram that shows what work items are included in the parent entity, how they are related to each other, and what results they are intended to achieve. Activity chart and network diagram are other examples of tools for visualizing sub-tasks and their hierarchical dependencies.
A typical sub-task is always:
- Possible only if its parent task is running
- Intended to achieve goals and objectives of the parent task
- Dependent upon other sub-task(s) within the same compound
- Managed under the same rules and requirements as the rest of the sub-tasks
- Performed by individuals and groups that work within the same compound.