Logical Relationships and Network Diagrams in Activity Sequencing
Project+ · Tools and Documentation · Bởi Super Admin
Master the four logical relationships between predecessor and successor activities—Finish-to-Start, Start-to-Start, Finish-to-Finish, and Start-to-Finish—and learn to create network diagrams.
Understanding Predecessor and Successor Activities
Once the activity dependency types have been identified, the next step is to determine the logical relationships between activities. A predecessor activity is one that comes before another activity, while a successor activity is one that comes after the activity in question. Understanding these relationships is fundamental to sequencing activities properly and determining whether activities can be scheduled in parallel or if one activity must wait until the predecessor task is completed. The logical relationship between predecessor and successor activities answers critical questions about how the dependency of one task impacts the start and finish of other activities associated with it. Does one activity have to start first? Can you start the second activity before the first activity is finished? All these variables impact what your overall project schedule looks like and involve establishing the logical relationship between the tasks so you can sequence them properly.
The distinction between predecessor and successor activities is essential for creating accurate project schedules. When a project manager understands which activities must precede others and which can follow, they can build a realistic timeline that reflects the actual constraints of the work. This understanding also reveals opportunities for parallel work, where multiple activities can occur simultaneously because they do not have a direct predecessor-successor relationship. By clearly identifying these relationships, project managers can optimize resource utilization and identify the critical path through the project.
The Four Logical Relationships
Finish-to-Start (FS) is a relationship in which the successor activity cannot begin until the predecessor activity has completed. This is the most frequently used logical relationship and is the default setting for most project-scheduling software packages. In a finish-to-start relationship, there is a clear sequential requirement: the predecessor must be entirely finished before the successor can start. This relationship is intuitive and reflects many real-world work scenarios where one task must be completed before the next can begin.
Start-to-Finish (SF) is a relationship in which the predecessor activity must start before the successor activity can finish. This relationship is seldom used in practice. In a start-to-finish relationship, the timing requirement is reversed from the typical finish-to-start pattern. The predecessor does not need to be completed, but it must have started before the successor can be finished. This unusual relationship appears in specific project scenarios but is not commonly encountered in typical project work.
Finish-to-Finish (FF) is a relationship where the predecessor activity must finish before the successor activity finishes. In this relationship, both activities may be running concurrently, but the successor cannot finish until the predecessor has finished. This allows for overlapping work where activities run in parallel but have a constraint on their completion timing. The finish-to-finish relationship enables schedule compression by allowing activities to start before their predecessors are complete, as long as the predecessor finishes before the successor finishes.
Start-to-Start (SS) is a relationship in which the predecessor activity must start before the successor activity can start. In this relationship, the successor can begin once the predecessor has started, but the predecessor must start first. Like finish-to-finish relationships, start-to-start relationships allow for parallel work and schedule compression. The successor does not need to wait for the predecessor to complete; it only needs to wait for the predecessor to begin.
Creating Network Diagrams for Activity Sequencing
One technique used by project managers to sequence activities is a network diagram, which depicts the project activities and the interrelationships among these activities. A network diagram is a great tool to develop with the project team. Using a whiteboard and labeling one sticky note with one activity makes it easy to see the workflow, and you can move the sticky notes around to make changes. This collaborative approach allows the team to visualize dependencies and adjust the sequence as needed.
The most commonly used network diagramming method is the precedence diagramming method (PDM). PDM uses boxes to represent the project milestones and arrows that represent activities. The arrows also show the dependencies between the tasks, making it easy to see which activities must precede others and which can occur in parallel. Once the activities are sequenced based on their logical dependencies, you are ready to assign resources to the activities and estimate how long it will take to complete each activity. The network diagram serves as the foundation for all subsequent scheduling and resource planning activities.
Thảo luận / Bình luận (0)
Chưa có thảo luận nào cho bài viết này. Hãy gửi bình luận đầu tiên nhé!
Vui lòng Đăng nhập để tham gia thảo luận.