NOTE ON CPM &

PERT
Certainly! CPM (Critical Path Method) and PERT (Program Evaluation and Review Technique) are two project management
techniques commonly used to plan, schedule, and manage complex projects. While they have similar goals, they approach project
management from slightly different angles and can be used together to create a comprehensive project management strategy.
Here's a brief overview of both techniques:

CPM (Critical Path Method):

CPM is a project management technique that focuses on identifying the critical path in a project schedule. The critical path is the
longest sequence of tasks and activities that determines the minimum time required to complete the project. CPM emphasizes time-
based scheduling and is particularly useful for projects where time constraints are crucial.

Key characteristics of CPM include:

1. Activity Sequencing: In 2. Activity Duration 3. Network Diagram: 4. Critical Path Identification:

CPM, tasks and activities are Estimation: Each CPM uses a network The critical path is
identified and arranged in a activity's duration is diagram, often determined by identifying the
sequential order. The estimated based on represented as a Gantt longest path of activities
relationships between tasks, historical data or expert chart, to visualize the through the network
such as dependencies and judgment. These project's activities, their diagram. Activities on the
constraints, are clearly defined. estimates help create a sequence, and their critical path must be
realistic project interdependencies. completed as scheduled to
schedule. prevent project delays.
PERT (Program Evaluation and Review Technique):
PERT is another project management technique that focuses on managing uncertain or unpredictable
activities in a project. PERT is particularly useful for projects with a high degree of uncertainty, where
accurate duration estimates are challenging.

Key characteristics of PERT include:

1. Three Time Estimates: PERT uses three time 2. Probabilistic Analysis: PERT employs
estimates for each activity: optimistic (minimum time), probabilistic techniques to calculate expected
pessimistic (maximum time), and most likely (best project durations and probabilities of meeting
guess). These estimates account for uncertainty and deadlines. This approach provides a more nuanced
variability in activity durations. understanding of project timelines.

3. Uncertainty Management: PERT focuses on identifying 4. Focus on Event Chains: PERT emphasizes
activities with the greatest uncertainty and potential impact the concept of event chains, which are
on the project timeline. This helps project managers sequences of events that can lead to delays if
allocate resources and attention where they are most any of the events in the chain are delayed.
needed.
In practice, CPM and PERT can be used together to provide a comprehensive project management approach.
CPM focuses on identifying the critical path and ensuring that the project is completed within the desired time
frame, while PERT provides a way to manage uncertainty and variability, helping project managers make informed
decisions about resource allocation and risk mitigation.

By combining the strengths of CPM and PERT, project managers can effectively plan, execute, and control
complex projects, accounting for both predictable and unpredictable factors that can influence project outcomes.
 FEATURES OF CPM & PERT
Features of CPM (Critical Path Method): Features of PERT (Program Evaluation and Review
Technique):
1. Deterministic Time Estimates: CPM relies on single-
point time estimates for each activity, assuming that 1. Probabilistic Time Estimates: PERT uses three time
activity durations are known with certainty. This makes estimates for each activity: optimistic, pessimistic, and most
CPM suitable for projects where activity durations can be likely. These estimates are used to calculate expected
accurately estimated. activity durations and to assess the variability and
uncertainty in project timelines.
2. Focus on Critical Path: CPM identifies the critical path,
which is the longest sequence of dependent activities that 2. Focus on Managing Uncertainty: PERT is particularly
determines the shortest project duration. Activities on the useful for projects with high uncertainty and variability in
critical path have zero float (slack), meaning any delay in activity durations. It provides a way to analyze and manage
these activities would delay the project. the impact of uncertain events on project schedules.

3. Project Schedule Emphasis: CPM places a strong 3. Emphasis on Event Chains: PERT considers the concept
emphasis on creating a detailed project schedule, usually of event chains, where a delay in one activity can trigger
presented as a Gantt chart, which illustrates the start and delays in subsequent activities. This highlights the
end dates of each activity and the overall project timeline. importance of managing dependencies and mitigating risks.
DIFFERENCES BETWEEN CPM &
PERT
1. Time Estimates: CPM uses deterministic time estimates, while PERT employs probabilistic time
estimates.

2. Focus: CPM focuses on time-based scheduling and identifying the critical path, while PERT
emphasizes uncertainty management and assessing the impact of risks.

3. Activity Variability: CPM assumes activity durations are fixed, while PERT accounts for the
variability and uncertainty in these durations.

4. Critical Path: CPM's critical path is determined by the longest sequence of dependent activities,
while PERT's critical path considers activities with the most impact on project duration due to
uncertainty.

5. Resource Consideration: CPM does not inherently consider resource constraints, whereas
PERT primarily deals with scheduling and uncertainty.

6. Project Types: CPM is well-suited for projects with known and certain activity durations, while
PERT is more suitable for projects with high uncertainty and variable durations.
 NETWORK DIAGRAM WITH AN EXAMPLE
A network diagram, often referred to as a "project network" or "activity network," is a graphical
representation of project activities and their dependencies. It helps visualize the sequence of
tasks, their relationships, and the critical path of a project. Let's explain the concept of a
network diagram using a simple example.

Example: Building a Website

Imagine you're tasked with building a website for a client. The project involves several tasks, such as designing the layout,
creating content, coding, and testing. Let's break down the tasks and their dependencies:

1. Design Layout (A) : This is the initial step, creating a visual representation of how the website will look.
2. Create Content (B) : Content needs to be created before it can be added to the website. This task can start once the layout
design is complete.
3. Code Website (C) : The coding of the website can begin once the content is ready.
4. Test Website (D) : Testing should be performed after the coding is done to identify and fix any issues.

Here are the task dependencies:

- Content creation (B) depends on layout design (A).

- Coding (C) depends on both content creation (B) and layout design (A).
- Testing (D) depends on coding (C).
 Now, let's represent this information in a network diagram:

Design Layout (A)

/ \
/ \
Create Content (B) Code Website (C)
\ /
\ /
Test Website (D)
In this network diagram:

- The nodes represent the tasks, labeled with their corresponding letters (A, B, C, D).
- The arrows between nodes indicate the dependencies. An arrow points from the task that needs to be completed first to the task
that depends on it.
To find the critical path using the network diagram, you would identify the longest path of dependent tasks. In this case, the
critical path is A -> B -> C -> D. Activities along the critical path must be closely monitored and managed to ensure the project is
completed on time.

Network diagrams become particularly useful when projects involve a larger number
of tasks with complex dependencies. They provide a visual overview that helps
project managers and teams understand the project structure, plan resource
allocation, identify bottlenecks, and ensure efficient project execution.
THANK YOU