| Content Levels | |
| Register for free access to papers, case studies, and over 50 templates. | |
| Subscribe for complete access: $14.95 monthly or $149/year | |
| Risk-free 15-day trial!
Compare levels View sample templates Corporate subscriptions | |
Quick Summary
This guideline illustrates how to identify work dependencies and provides a table for capturing them. Third in a series—see the Related Templates below for the others.
What this is
This is the third in a series of templates for project plan and schedule development. This guideline illustrates the process for identifying work dependencies and provides a table for capturing these dependences. This process can be done before actual schedule creation in a tool, as it often leads to some repartitioning of the tasks in the work breakdown. Though software scheduling tools have powerful graphical interfaces for entering and managing task dependencies, doing an initial manual pass at high-level dependencies may actually help you repartition the tasks more efficiently, before estimates and dates add another level of complexity to the plan.
Why it's useful
Engaging in a dependency discussion is a logical step after the tasks are defined and some initial resource assignments are made, because this often has a major impact on the work definition and breakdown and subsequent estimates. It also acts as a communication stimulus among the team to better understand the inter-relationships and dependencies among their work. Dependency work usually results in some repartitioning of the tasks, so this process may be done iteratively with the preceding work breakdown efforts.
How to use it
©Copyright 2000-2010 Emprend, Inc. All Rights Reserved.
About us Site Map View current sponsorship opportunities (PDF)
Contact us for more information or e-mail info@projectconnections.com
Terms of Service and Privacy Policy