Previous
¶ Dependency Analysis
¶ What it is
Dependencies are the relationship or links between tasks that define the features or tasks. Dependency analysis identifies, predicts, and manages the dependencies between tasks, personnel, processes, and systems.
¶ Why it is useful
Dependency analysis is the key to project planning, most feasibly and reasonably.
It secures the project's progress and foresees future issues and risks so the project managers and persons in charge can identify the right stakeholders and plan for cross-team collaboration.
In project management, no surprise is welcomed.
¶ When to use it
Dependency analysis must be done as early as possible during all phases of a project life cycle.
At the latest, the dependency list must be ready for alignment during the project kickoff meeting. Dependency analysis must be done once before the project gets kicked off, as all the stakeholders must have an overview of the issues or risks during the kickoff.
¶ How is it done
- Go over the product roadmap and understand the short-term and long-term objectives.
- Check what’s missing internally & externally.
- Prioritise the actual dependencies that impact the most
- Sort out the owners and parties of the dependencies
- Check timeline, dependency types, and dependency estimated resolution time
- Plan for dependency resolution due date and put it into the timeline
- Accelerate if there is anything out of reach or control
There are generally four types of dependencies:
- Finish-to-start (FS): A task's finish date drives another's start date. One element requires the completion of another before you can start it
- Finish-to-finish (FF): A task's finish date drives another's finish date.
- Start-to-start (SS): The first element must start before the second one can begin.
- Start-to-finish (SF): A task's start date drives another's finish date.software
¶ Do's & Don't
Do's
- Set up SOPs to avoid mistakes or misconsideration.
- Maintain a regular dependency checklist for each kind of project and each phase of the project. Please review and adjust it to keep it up-to-date.
- Always update the profile of the persons in charge for each kind of dependency in case you encounter any unexpected but urgent dependency.
Don't
- Don’t leave the dependencies alone after identifying and assigning them.
- Please don’t check the dependency status only before the deadline, but analyse it regularly or as planned.
¶ Tools needed
- Kanban boards
- Gantt charts
- Calendars
- And other project management softwares
¶ Example
Here is a checklist example of common dependencies. It’s important to go over the possible dependency checklist ahead of the project and plan the coordination in advance. However, the types in the real world are not limited to this example.
