Schedule dependencies designed to measure and define activities done by multiple resources for single process flow. In IT, we can manage proper utility of team according to the role of responsibility by designing Schedule dependency matrix.
Schedule dependencies helps to ensure optimum utilization of resource. In IT, once company grow with more then 100 front line developers, then it is very hard to manage process flow with best resource investment plan for capability utilization. By identifying schedule dependency event matrix, we can stream line entire project execution process more effectively.
Lets check Schedule Dependency Matrix with relevant example:
A: FS [ Finish to Start]
Task “A” FS Task “B”
The first task (A) finishes before the second task (B) can start
Example : Once client approve design, developer can start coding or HTML conversion of PSD.
B: FF [Finish to Finish]
Task “A” FF Task “B”
The first task (A) should be finished before the second tasks (B) could get finish
Example : BD can not send project status mail to client before Project Manager calculate progress report.
C: SS [ Start to Start ]
Task “A” SS Task “B”
The second task (B) cannot start until the first task (A) get started
Example: Client should escrow [ pay ] Advance payment to start Project SRS / Coding.
D: SF [ Start to Finish ]
Task “A” SF Task “ B”
The second task (B) cannot finish before the first task (A) has started
Example: The first shift’s online chat support executive cannot leave office until the second shift’s online chat support executive come to office.
Schedule Dependency matrix is very simple yet effective to identify and streamline project and process flow. If we know the cycle of finishing task A then we can arrange task B accordingly. That helps in project execution plan, change request, client communication or PMS, and resource arrangement for better service.