Unleashing the Power of AI: Revolutionizing Customer Success Teams
In today’s rapidly evolving business landscape, organizations are constantly looking to find innovative ways to improve customer satisfaction and retention....
In project management, a dependency is what we call the relationship between two tasks when action or activity on one determines key dates for the other. Start and finish dates of the task are the focus of the relationship between a predecessor and successor activity with four types of logical relationships:
Finish to Start (FS): This is the most common dependent relationship and it occurs when the successor task cannot start until the predecessor task is finished. Examples of FS dependency might be that the building the walls must finish before the roof installation can start or when configuration can’t begin until the design is complete.
Start to Start (SS): These relationships occur when the successor task cannot start until the predecessor has started. This is done to optimize the project schedule and make efficient use of project resources. Examples of SS dependency might be that mortar is mixed at the same time tiling is started or if an external press release is sent out at the same time an internal announcement is made.
Finish to Finish (FF): These relationships occur when the successor task and the predecessor task need to finish at the same time, again to optimize the use of project resources. Examples of this might be finishing the plumbing and electric so that the inspector only comes once or it might be that configuration and testing complete at the same time to account for client feedback.
Start to Finish (SF): In this relationship, we see that the successor cannot finish until the predecessor has begun. An example might be that the inspection cannot be scheduled until a building permit is requested or Sign Off cannot be complete until UAT has begun.
Though dependencies between tasks are common, it is not required for a task has a dependent relationship with another. A task can be both a successor and a predecessor to other tasks, it can have multiple relationships of the same type, or it could have no dependencies at all. Consider a task like building the walls; this task might be the predecessor to installing the roof, and also the successor to laying the floor.
The way these relationships trickle downstream throughout the project will influence its schedule. When a task is early or late to start or finish how might that impact the start or end date of the successor task and all the other tasks in the line? Managing and monitoring dependencies are part of a project manager’s role and knowing whether a task that finishes early is a benefit to be exploited or a risk to be mitigated can be pivotal for a successful project outcome and a satisfied client.
AUTHOR
Phil De Gruchy
Related Articles
How Project Overruns Impact your Bottom Line — and How Cloud Coach is Closing the Revenue Leak
Your projects are overrunning. And it’s costing your business more money than you think. The causes of overrun are varied;...
Erik Rozynes
Nov 14 2024 8 min read
Integrating Cloud Coach and Jira for Optimized Project Management
Are you a Cloud Coach user (or even thinking about using Cloud Coach) and wondered whether we can integrate with...
