Project Managers are always playing around with dependencies. It could be dependencies with your vendors or suppliers or peer teams or project team members.
In reality , you will hardly find a project without dependencies. If not external definitely we will have internal ones.
There will be deliverables from parties who are beyond your span of control. But your deliverables will have dependencies on those. Any delay can impact your project.
The following can help in managing those
- During project planing stage identify your dependencies also.
- Create a Summary task in MS Project and capture your dependencies under that.
- On the tasks which are under your scope & control, set the predecessor field to appropriate tasks captured under your dependency summary task.
- It’s a good practice to set a finish date for the external dependencies. To do that, you need to work backwards. Look at the task which has a dependency on the external dependency. Use your judgment and identify a delayed start date, the task can absorb without jeopardising the overall project time lines. ( That start date – ‘y’ number of days ) would be your external dependency’s finish date. Choose ‘y’ based on your comfort level.
- Utilize the project review calls to keep a tab on the progress by external teams. You can raise a flag based on the info you have captured on the dependency and your task as in step(4)
- Task Dependencies Help Manage the Interconnections in Project Plans (workzone.com)
- Project Controls, Part 2- Controlling Schedules and Budgets (vistage.com)
No two projects are same. But you will still find some items repeating in each and every project. So also is the fact that each project will come across areas of improvement.
How do you ensure that we don’t miss out those common tasks in our next project?
The common tasks could be part of the process followed at the organizational level or by the nature of the project. A project manager who have executed project in the organization in the past, will be aware of those. But how about a project manager who joined your organization recently and about to start with his maiden project?
Having this mandatory tasks or items as stipulated by the organization or type of project captured in a project plan template helps in addressing this scenario.
How do you ensure that the mistakes made in the current project are not repeated in future projects?
Lessons learned is the formal way of addressing this. You can maintain a centralized repository with adequate indexing and search criterion , so that its easy to find what you are looking for. But this still doesn’t ensure that we will miss something in future.
Each lessons learned will end up with a recommendation on how this mistakes can be avoided. And this recommendations should be implemented either on the processes or templates or tools used for project management.
So if any of the recommendations can be addressed by including that as a task in a project plan, then a project plan template is the right place.
Project Management Office(PMO) owners change, so will Project Managers. But embedding the best practices or lessons learned in our processes , templates and tools ensures that experience gained by our predecessors are utilized by future team.
Last but not the least, have your project plan template available on a centralized repository. And make it mandatory to Project Managers to always use a template to start off with their individual project plan.
See Also : More articles on MS Project