You need to consider dependencies as you work through the order of tasks in your plan. Let’s say we are still building that fence that we used as an example when defining project scope. You need to dig post holes before you can put your posts in place. So the task of erecting posts is dependent on the task of digging post holes. You need to have the fence in place before you can paint the fence. So the task of painting is dependent on the task of fencing.
It could be that a task can be dependent on more than one other task or chain of tasks. For example, in the fencing example you might have a group of tasks which are about procuring and preparing material: buying timber, cutting timber, buying hardware and tools. You might have another set of tasks which are about preparing the land, staking out the fence, digging post holes. The set of tasks required to erect the fence is dependent on the tasks required to prepare materials, and the tasks required to prepare the land.
 |
| In this example the "Build" tasks are dependent on both the "Design & Prepare" tasks & the "Prepare Boundary" tasks. |
You might also have other dependencies: on other projects (the project you are running to build a gate), or other suppliers (who will provide the fancy hinges you want for your gate), or on particular date (the date you get back from your overseas trip).
As project manager you can also question your dependencies in an attempt to find quicker or better ways of doing things. Did you see that earlier I said you had to put your fence up before you could paint it? Is that true, could it be possible, or even easier, to paint some of the components of the fence before you build it? Questioning your dependencies like this might help you find a better way of doing things.
As a project manager you need to be aware of all dependencies so that you can include them in your plan and have your plan be a more reasonable forecast of reality. If you’re not aware of dependencies you might find your project stuck, waiting for something to complete before you can move on.
So make sure you understand your dependencies, otherwise you will have problems –you can depend on it! (ouch).
