We’ve said it before and we’ll say it again: projects don’t exist in a vacuum. Like successful communities, a project is very much dependent on what is going on around it.The context of the project really makes a difference to how successful it is and how the team performs.
Identifying project dependencies is part of the activity of setting up a project, so if you have run a project before, you have probably done the exercise in which you get the team together to talk about where this piece of work overlaps with others. But did you know that you could make that job easier by thinking about the 4 types of dependency? If you use these categories, you can brainstorm more effectively and you will probably identify a few more dependencies to write down in your project charter.
Let’s just be clear on what a dependency is first, before we start looking at the different types. A project dependency is the relationship that links the order in which activities are carried out (these are shown by the lines on a Gantt chart that join up tasks) but it’s a bit wider than that as well. Projects are also dependent on what is happening elsewhere in the company. So let’s look at those 4 types of dependency.
1. In-Company, In-Project
This is the most common type of dependency and the one that you and your project team are probably …Read More