Sekwencjonowanie działań oznacza ustalanie logicznego porządku realizacji zadań projektowych, z wykorzystaniem diagramów sieciowych.
Główne techniki tworzenia diagramów:
Rodzaje zależności logicznych:
Lag i Lead:
Typy zależności:
Zrozumienie sekwencjonowania działań, zależności między nimi oraz technik wizualizacji takich jak PDM, AON, Gantt czy PERT pozwala efektywnie planować i kontrolować harmonogram projektu. W kolejnej lekcji stworzymy przykładowy diagram sieciowy.
Sequencing Activities in Project Management
In our project management journey, we have developed the schedule management plan and identified the key activities and milestones. The next essential step is to sequence these activities effectively.
Understanding Activity Sequencing
Sequencing means arranging the activities in a logical order. To do this, we use network diagrams, also referred to as schedule network diagrams or activity network diagrams. All three terms refer to the same concept.
Once we create the network diagram, we can later perform schedule calculations based on this visual representation. However, for now, we will focus only on creating the network diagram, without performing any calculations.
Techniques for Drawing Network Diagrams
There are three common methods for drawing network diagrams:
•Precedence Diagramming Method (PDM): Also known as Activity on Node (AON). This is the primary method used in most project management tools and is the most relevant for the exam.
•Arrow Diagramming Method (ADM): Also known as Activity on Arrow (AOA). This technique represents activities with arrows.
•Graphical Evaluation and Review Technique (GERT): A more advanced and less commonly used method, often excluded from standard exams.
When using PDM, we represent activities using rectangular nodes (boxes), and dependencies are shown with arrows connecting the boxes.
Types of Dependencies (Logical Relationships)
There are four types of relationships between activities:
•Finish-to-Start (FS): The most common type. Activity B cannot start until Activity A finishes.
•Start-to-Start (SS): Activity B cannot start until Activity A starts.
•Finish-to-Finish (FF): Activity B cannot finish until Activity A finishes.
•Start-to-Finish (SF): Rarely used. Activity B cannot finish until Activity A starts.
Lead and Lag
•Lag: A delay between activities. Example: Activity B starts 2 days after Activity A finishes (FS + 2d).
•Lead: An overlap between activities. Example: Activity B starts 2 days before Activity A finishes (FS – 2d).
Types of Dependencies
•Mandatory (Hard Logic): Inherent constraints, such as needing to finish coding before testing.
•Discretionary (Soft Logic): Preferred order based on experience or best practices.
•External Dependencies: Driven by outside parties, such as regulatory approvals.
•Internal Dependencies: Driven by conditions within the project team or organization.
By mastering these concepts, you are prepared to build network diagrams and understand how activity relationships impact project schedules. In the next lesson, we will explore how to construct and analyze network paths and calculate the critical path.