Module 4: Project Techniques

Project techniques refer to the specialized procedures and tools used to

initiate and execute a project, ultimately delivering a desired
outcome. These techniques help teams focus on objectives and
efficiently manage resources, time, and scheduling, ensuring projects
are completed successfully.
Project Management Methodologies:

Waterfall:
A sequential approach where each phase (initiation, planning, execution, monitoring, and closeout) must be
completed before the next begins.
Agile (Scrum):
An iterative and flexible approach that breaks projects into short cycles (sprints) and allows for continuous
feedback and adaptation.
Kanban:
A visual workflow management system that helps teams move work through a process efficiently, often used in
software development but applicable to various projects.
Extreme Project Management (XPM):
Focuses on managing complex and rapidly changing projects by breaking them into short cycles and tracking
progress frequently.
Rational Unified Process (RUP):
An iterative development methodology that focuses on delivering projects in iterations, breaking them down into
smaller, manageable segments.
Adaptive Approach:
A flexible and responsive approach that allows for changes in scope while maintaining time and cost constraints.
Planning and Scheduling Techniques:
Gantt Chart:
• A visual representation of project timelines and tasks, showing dependencies and progress.
Critical Path Method (CPM):
• Identifies the most critical tasks that, if delayed, will impact the overall project completion
time.
Program Evaluation and Review Technique (PERT):
• A technique that helps estimate project completion time by considering optimistic, pessimistic,
and most likely durations for tasks.
Work Breakdown Structure (WBS):
• A hierarchical decomposition of a project into smaller, manageable tasks.
Event Chain Methodology:
• A method that focuses on managing both expected and unexpected events that can affect
project planning.
Work Breakdown Structure (WBS)

The Work Breakdown Structure (WBS) requires you to break down your
project into its parts — i.e. smaller and more manageable pieces.
According to A Guide to the Project Management Body of Knowledge,
work decomposition needs to be done “to accomplish the project
objectives and create the required deliverables.”
Within the Work Breakdown Structure, you need to properly:
Identify,
Estimate,
Budget, and
Schedule your work.
How to use the Work Breakdown Structure?

Use WBS to break down complex project tasks into smaller tasks until
you can no longer subdivide these tasks. Smaller tasks are easier to
work with since it’s easier to estimate the time requirements and the
cost to complete them.
When you decompose your project to the lowest levels in WBS, those
levels are called work packages. When you identify them, you can easily
and safely estimate costs and time for the work together with
controlling and managing them efficiently.
Most projects have a similar life cycle. So, you can use standard WBS
templates to modify them to fit your projects.
Gantt chart

A Gantt chart is one of the oldest project management techniques. It’s

a horizontal bar chart that illustrates a project’s schedule. Each activity
in the project is represented by a bar, and its length represents the
duration of each task — its start and finish dates.
The position of the bar is also important since it stands for the
scheduling of the task. If one task follows another, it means the task is
dependent upon the completion of the predecessor task to get started.
You may also see other geometrical signs within the chart, such as a
diamond or triangle-shaped symbol that represents an important
milestone during a project. The Gantt chart is widely known for its
simplicity and low cost.
How to use a Gantt chart?

Gantt charts are most useful for simple projects. You can implement your Gantt
chart by:
• Setting up details of your project,
• Adding and scheduling project tasks,
• Inserting important milestones, and
• Establishing task dependencies.
Gantt charts are best for teams who need project complexity across industries
like:
• Software development,
• Design,
• Manufacturing,
• Marketing, and others.
Networks Analysis
In project management, network analysis uses visual representations
(networks) to depict project activities, dependencies, and timelines, enabling
better planning, scheduling, and control, particularly for complex projects.
Visual Representation:
• Network analysis uses diagrams (networks) to show project activities as
nodes and their dependencies as arrows or lines.
Activity-on-Node (AON):
• A network diagram where activities are represented by nodes and
dependencies are shown by arrows connecting the nodes.
Activity-on-Arrow (AOA):
• A network diagram where activities are represented by arrows and the nodes
represent events or milestones.
Critical Path Method
The Critical Path Method (CPM) in project management is a technique that identifies the
longest sequence of tasks (the "critical path") that must be completed on time to finish the
project, highlighting tasks that, if delayed, will delay the entire project.
Identifying the Critical Path:
The CPM helps determine the critical path, which is the sequence of activities that
determines the shortest possible project completion time.
Dependency Management:
It involves mapping all project activities, their dependencies, and estimated durations.
Project Planning and Scheduling:
CPM is used for analyzing, planning, and scheduling large, complex projects.
Preventing Delays:
By focusing on the critical path, project managers can proactively address potential delays
and ensure timely project completion.
Key Steps in CPM:
List all project activities: Break down the project into individual tasks or
activities.
Identify dependencies: Determine which activities must be completed before
others can begin.
Create a network diagram: Visually represent the project activities and their
dependencies.
Estimate activity durations: Determine how long each activity will take to
complete.
Calculate the critical path: Identify the longest path through the network
diagram, representing the shortest possible project completion time.
Calculate float: Determine the amount of time an activity can be delayed
without delaying the project's completion.
Basic steps in CPM
The basic steps in the Critical Path Method (CPM) involve identifying project activities, defining their
sequences and dependencies, creating a network diagram, estimating activity durations, identifying
the critical path, and updating the diagram as the project progresses.
Step 1: Identify Each Activity: List all the tasks or activities required to complete the project.
Step 2: Establish Dependencies: Determine the sequence and dependencies between activities,
identifying which tasks must precede others, which can be done concurrently, and which must
follow.
Step 3: Draw the Network Diagram: Create a visual representation of the project's activities and
their relationships, using arrows to show dependencies.
Step 4: Estimate Activity Completion Time: Estimate the time required to complete each activity.
Step 5: Identify the Critical Path: Analyze the network diagram to identify the longest path through
the project, which represents the critical path (activities that cannot be delayed without delaying
the entire project).
Step 6: Update the Critical Path Diagram to Show Progress: As the project progresses, update the
network diagram to show actual completion times and any changes to the critical path.
Rules for drawing network diagram
To draw an effective network diagram, remember these key rules: activities are represented by
arrows, events by circles, flow is from left to right, each activity must start and end at a circle,
and networks have only one initial and one final event.
1. Representing Activities and Events:
Activities: Represent tasks or work items with arrows.
Events: Represent milestones or points in time with circles.
Each activity must start and end at a circle (event).
2. Network Flow:
Direction: The network diagram should flow from left to right, representing the sequence of
activities.
Precedence: Activities can only start once all preceding activities are completed.
No Loops: Avoid creating loops or cycles in the diagram.
No Dangling Arrows: Ensure all arrows connect to events (circles).
Labeling and time estimates
"labeling" refers to adding descriptive tags or labels to data, while "time estimates" are
estimations of how long tasks or projects will take, often used for planning and tracking progress.
• Labelling:
• Data Annotation:
• In machine learning, labeling involves annotating data (images, text, etc.) with relevant
information to train models.
• Purpose:
• Labels provide context and allow algorithms to learn and make predictions.
• Examples:
• Image Recognition: Labeling images as "cat", "dog", or "car".
• Text Classification: Labeling text as "spam" or "not spam".
• Time Series Data: Labeling time series data with events or states.
Time Estimates:
• Project Management: Time estimates are used to plan and track project progress.
• Task Estimation: Estimating how long individual tasks will take.
• Project Duration: Estimating the overall project duration.
• Units: Time estimates can be in minutes, hours, days, or weeks.
• Tools: Project management tools like Jira use time estimates for tracking progress.
Examples:
• A task might have a time estimate of "2 hours".
• A project might have a time estimate of "3 weeks".
Types of Estimates:
• Original Estimate: The initial estimate made at the start of a task or project.
• Remaining Estimate: The estimated time remaining to complete a task or project.
• Time Spent: The actual time spent on a task or project.
Project Evaluation and Review Technique (PERT)
PERT (Program Evaluation and Review Technique) is a project
management tool used to schedule and coordinate tasks by identifying
dependencies, estimating task durations (optimistic, most likely, and
pessimistic), and determining the critical path (longest path) for project
completion.
• Purpose:
PERT helps project managers plan, schedule, and control projects by
visualizing tasks, dependencies, and potential delays.
• PERT Chart:
A visual representation of project activities and their dependencies,
often using nodes and arrows.
PERT
• Critical Path:
The longest sequence of activities in a project, determining the
minimum time required to complete the project.
• Three-Point Estimating:
PERT uses three time estimates for each activity: optimistic (best-case
scenario), most likely (realistic scenario), and pessimistic (worst-case
scenario).
• Expected Time (te):
A weighted average of the three time estimates used to calculate the
expected time for each activity: te = (o + 4m + p) / 6.
Steps in PERT:
• Identify Project Activities: Define all tasks and milestones required for project completion.
• Determine Dependencies: Identify which activities must be completed before others can start.
• Draw a PERT Chart: Visually represent activities and their dependencies using nodes and
arrows.
• Estimate Activity Durations: Assign optimistic, most likely, and pessimistic time estimates for
each activity.
• Calculate Expected Time (te): Use the formula (o + 4m + p) / 6 to calculate the expected time
for each activity.
• Identify the Critical Path: Determine the longest path through the PERT chart, which dictates
the minimum project completion time.
• Analyze Slack: Identify activities that have slack (extra time) and can be delayed without
affecting the overall project timeline.
• Monitor and Control: Regularly review progress, identify potential problems, and adjust the
plan as needed.
Benefits of Using PERT:
• Improved Planning:
PERT helps project managers create a clear and detailed project plan.
• Better Coordination:
The visual nature of PERT charts facilitates better communication and coordination
among team members.
• Early Problem Identification:
PERT helps identify potential delays and bottlenecks early in the project lifecycle.
• Realistic Time Estimates:
By using three-point estimating, PERT provides more realistic time estimates for project
activities.
• Effective Resource Allocation:
PERT helps identify critical activities and allocate resources effectively.
Example:

• Imagine a project with three activities: A, B, and C.

Activity A: Optimistic = 2 days, Most Likely = 4 days, Pessimistic = 6 days
Activity B: Optimistic = 3 days, Most Likely = 5 days, Pessimistic = 7 days
Activity C: Optimistic = 1 day, Most Likely = 3 days, Pessimistic = 5 days
• Using the PERT formula, the expected time for each activity is:
Activity A: (2 + 4*4 + 6) / 6 = 4.67 days
Activity B: (3 + 4*5 + 7) / 6 = 5.83 days
Activity C: (1 + 4*3 + 5) / 6 = 3.33 days
Project delays
Project delays, or the failure to meet planned deadlines, can stem from various factors, including
poor planning, resource constraints, scope creep, and external factors, impacting timelines,
budgets, and stakeholder satisfaction
What are Project Delays?
Definition:
Project delays occur when a project falls behind its planned schedule, meaning tasks or milestones
are not completed on time.
Impact:
They can lead to missed deadlines, budget overruns, and even project derailment.
Causes:
Internal Factors: Poor planning, inadequate resource allocation, lack of communication, and scope
creep.
External Factors: Weather, material shortages, supplier issues, and unforeseen events.
Delays
• Consequences:
• Financial: Increased costs due to overtime, re-planning, and potential
penalties.
• Reputational: Damage to the project team's reputation and client
relationships.
• Operational: Delays can lead to missed opportunities, reduced
productivity, and increased stress.
Common Causes of Project Delays:

Poor Planning:
• Inadequate initial planning, unrealistic timelines, and insufficient risk assessment can lead to
delays.
Resource Constraints:
• Lack of sufficient resources (human, financial, or material) can hinder project progress.
Scope Creep:
• Uncontrolled changes to the project scope without corresponding adjustments to timelines and
resources.
Communication Issues:
• Poor communication among stakeholders can lead to misunderstandings, conflicts, and delays.
• External Factors:
Weather, material shortages, supplier issues, and unforeseen events can disrupt project
schedules.
Steps to be followed during project delay
To effectively manage a project delay, immediately assess the situation,
communicate transparently with stakeholders, analyze the root cause,
develop a recovery plan, and monitor progress closely.
Assess the Situation:
• Acknowledge the delay: Don't try to ignore or downplay the issue.
• Identify the root cause: Determine what caused the delay (e.g.,
resource shortage, scope change, unexpected issue).
• Evaluate the impact: Assess the impact on the project timeline,
budget, and resources.
Steps
2. Communicate Transparently:
• Inform stakeholders: Keep all relevant stakeholders (team members, clients, etc.) informed about
the delay and its potential impact.
• Be factual and objective: Explain the situation clearly and avoid making excuses or assigning blame.
• Provide realistic timelines: Offer a clear and realistic assessment of the expected delay and the
steps being taken to mitigate it.
• Maintain regular updates: Keep stakeholders informed about progress and any changes to the
plan.
3. Develop a Recovery Plan:
• Prioritize tasks: Identify critical tasks and reallocate resources as needed to expedite them.
• Revise the schedule: Adjust the project timeline to account for the delay.
• Implement solutions: Develop and implement a plan to address the root cause of the delay and get
the project back on track.
• Seek expertise: If necessary, bring in experts to address specific challenges.
4. Monitor Progress and Learn:
• Track progress: Regularly monitor progress against the revised
schedule and recovery plan.
• Identify and address new issues: Be proactive in identifying and
addressing any new issues that arise.
• Document lessons learned: Review the delay and its management to
identify areas for improvement in future projects.
Project evaluation
Project evaluation is a systematic process of assessing a project's effectiveness, efficiency, and impact, helping to
identify areas for improvement and inform future decisions. It involves gathering and analyzing data to determine
if the project met its goals and objectives.
• What is Project Evaluation?
Definition:
• Project evaluation is a structured process of assessing a project's performance, outcomes, and impact.
Purpose:
• To determine if a project achieved its intended goals and objectives.
• To identify areas for improvement in future projects.
• To inform decision-making and resource allocation.
• To ensure accountability and transparency.
Process:
• Data Collection: Gather data on project activities, outputs, outcomes, and impacts.
• Data Analysis: Analyze the collected data to identify strengths, weaknesses, and areas for improvement.
• Reporting: Prepare reports summarizing the evaluation findings and recommendations.
Types of Evaluation:
• Formative Evaluation: Conducted during the project lifecycle to
monitor progress and make adjustments.
• Summative Evaluation: Conducted at the end of the project to assess
overall success and impact.
Evaluation Criteria:
• Relevance: Does the project address a real need or problem?
• Effectiveness: Does the project achieve its intended outcomes?
• Efficiency: Are resources used effectively and efficiently?
• Impact: What are the long-term effects of the project?
• Sustainability: Can the project's benefits be sustained over time?
Abandonment analysis
Abandonment analysis is a decision-making process that determines
whether a project should be stopped before its planned completion. It
involves evaluating the potential benefits and drawbacks of continuing
a project versus abandoning it, often considering factors like cash flow,
remaining investment, and potential liquidation value.
• Why is Abandonment Analysis Important?
Project Failure:
• Abandonment analysis helps assess whether a project is likely to fail
or if its performance is significantly below expectations.
• Resource Allocation:
It helps allocate resources effectively, guiding decisions on which
projects to continue investing in and which to abandon.
• Cost Optimization:
Abandonment analysis can help minimize costs by stopping projects
that are not generating sufficient returns.
• Market Changes:
It allows businesses to adapt to changing market conditions and
abandon projects that are no longer viable.
 Key Considerations in Abandonment Analysis:
• Project Performance:
Evaluate the project's current performance, including cash flow, profitability, and other
key metrics.
• Remaining Investment:
Determine the amount of investment required to complete the project and the
potential costs of abandoning it.
• Abandonment Value:
Calculate the value of the project's assets if they were liquidated immediately, also
known as the liquidation value.
• Future Potential:
Consider the potential for future revenue or cost reductions if the project is continued.
• Opportunity Costs:
Evaluate the potential returns from investing resources in alternative projects.
• 3. Decision-Making Framework:
• Net Present Value (NPV):
Compare the NPV of continuing the project with the NPV of abandoning it.
• Break-Even Analysis:
Determine the point at which the project becomes profitable or if it's likely to remain
unprofitable.
• Decision Tree Analysis:
Develop a decision tree to model the potential outcomes of continuing or
abandoning the project, considering various scenarios and probabilities.