Project Management - Dependencies

Entering tasks into your project management scheduling application can be as easy entering items in a spreadsheet. Creating dependencies so the tasks have a flow towards a deliverable can require a good deal of additional thought and discussion.

Many project schedules, used as part of an overall project plan, end up being a list of tasks, with the number of hours, or days, to execute the task, and who is assigned as the only pertinent information.

The key advantage of entering the predecessor, and successor of the task is the determination of the tasks critical to the delivery of the project. This term is the "critical path." Some project schedulers can highlight the critical tasks in red, which is a quick and efficient method.

A simple example of dependencies
1.1) Determine and document the time management plan (e.g. schedules review)
1.2 ) Determine and document the communications management plan (e.g. email, texting, voice mail, status reports, signed SOW)
1.3)  Determine and document the quality management plan (QA, QC-evaluate product
1.4)  Determine and document the human resources management plan (Team member acquisition/development)
1.5)  Determine and document the cost management plan (Estimates / Budget)
1.6)  Determine and document the risk management plan (planning, monitoring, control)
1.7)  Determine and document the procurement management plan (contract admin/ closeout)
1.8) Determine and document the integration plan
1.9) Determine and document the scope plan
1.10)  Review and Accept the overall project plan (Tasks 1.1 to 1.9 must be completed prior to executing Task 1.10)

Understanding which tasks must be executed, and in which particular order can ease the delivery of the project, and provides a "blueprint" for the team to follow.