How to Establish Dependencies between Tasks in Project Breakdown

Dependencies show specific relationship between two or more tasks which belong to one and the same project. In a project breakdown design task dependencies identify how tasks relate to each other, what common objectives they deal with, and under what constraints they are supposed to be performed.

There are 5 general steps for establishing dependencies between tasks in project breakdown:

1. Identification: a project is identified and its objectives are established; major tasks of the project are outlined.
2. Definition: major tasks are defined and their goals are described and aligned with project objectives.
3. Estimation: an analysis of constraints (time, scope, quality, performance, labor, etc.) is performed to estimate and determine resources required for project tasks; project milestones are set.
4. Division: decomposition of the project and its tasks into sub-projects and sub-tasks is done; major levels of project breakdown are defined; resources are allocated among major levels.
5. Design: a decomposition chart of the project is designed; this chart includes major tasks, milestones, resources and breakdown levels.

CentriQS Task Dependency Solution CentriQS lets users set "Finish-to-Start" task dependency when depending task cannot begin until dependent-on task is completed. As soon as predecessor-successor relationship between the tasks is set, successor task gets state 'Blocked' with reason 'By predecessor' and only after predecessor is done, successor gets unblocked. Assigned users can get notifications both when their tasks get blocked and unblocked.