The Network Diagram is the main output of the third process in Time Management, Sequence Activities process. Sequence Activities process sequences the activities that have been defined in the define activities process. Because different activities will depend on each other. The Network diagram shows the interrelationship between activities and boxes. Precedence Diagramming Method is the most popular method to draw network diagrams. Naturally, there will be relationships and dependencies among the activities in Precedence diagramming Method.
Take part in our 100% online & self-paced 1-hour PMP training.
You will receive detailed training on these relationships if you sign up for a project management certification course. Because PMP exam questions often include questions about Time Management. This knowledge area and its processes should be included in your PMP study plan. We will also be discussing the types of relationships that Precedence Diagramming Method uses, and giving real-life examples.
The 4 Types Relationships in Precedence Diagramming Method
To complete the network diagram for a project using the method, four types of relationships are used between the activities. These relationships are:
Let’s look at each type of dependency.
The first type of dependency is Finish to-Start dependency, also abbreviated as FTS. This is the most commonly used dependency type between activities. If an activity cannot begin before the previous activity finishes, then there must be a finish-to start dependency between these activities. In a construction project, for example, you cannot paint the building before it is completed. You cannot test a screen in a software project before it is finished. These are examples of start-to-finish dependencies in the activities of Precedence Diagramming method.
The second type of dependency is Start to-Start dependency, also abbreviated as SS. This dependency indicates that two activities will begin together. In a construction project, the procurement of materials will be the first step in building the mainframe. These activities will be shown in the network diagram as dependent from start to finish.
The third type of dependency is Finish to Finish dependency, also abbreviated as FF. This dependency indicates that two activities within a project will end together. In a software project, bugs can be discovered during testing. These bugs will be fixed and reported to the software developers. The software developers will fix the bugs. However, the testing team must verify that the bug has been fixed. Testing and bug fix activities are examples of a finish-to-finish dependency in the Precedence Diagramming Model.
Precedence Diagramming Method’s fourth type of dependency is the Start-to-finish dependency, also abbreviated as SF. This type of dependency is very rare in projects. Activity B cannot finish after Activity A has started. These relationships can be used for just-in-time supply chains materials, for example. Let’s say you work in a car manufacturer company. In your assembly line, an electrical component is used. This component is supplied by a supplier. Let’s say that you have 100 components in your warehouse. You have a limit that says if the number of components in your warehouse falls below 20, you should place a new order with the supplier of the electronic part. In this instance, there is a Start to Finish dependency between the remaining electronic components in the warehouse as well as placing a new order.
What is GERT?
GERT can be described here. GERT is a modification of the ne