Project Management

Project Management Approaches

Project

A temporary endeavor undertaken to create a unique product, service, or result. Unlike ongoing operations, a project has distinct start and end dates, specified resource constraints, and highly specific, measurable objectives.
  • Traditional (Waterfall): A linear, sequential approach where each project phase must be completed before the next begins. Requirements are locked in early. Best for physical construction (you cannot pour a foundation while designing the roof).
  • Agile Project Management: An iterative, incremental approach that emphasizes extreme flexibility, continuous customer collaboration, and rapid responses to change. Work is done in short cycles (sprints). Best for software engineering or R&D where end goals are initially ambiguous.

The Project Life Cycle

The project life cycle provides a predictable framework for managing the complexities of an engineering project. It typically consists of five distinct, yet overlapping phases:

Procedure

  1. Initiation: Defining the high-level project scope, identifying key stakeholders, and obtaining official authorization (usually via a Project Charter) to begin allocating resources.
  2. Planning: Establishing the detailed scope, defining objectives, developing the Work Breakdown Structure (WBS), and creating comprehensive schedules, budgets, and risk management plans.
  3. Execution: The phase where the actual work is performed. Resources are deployed, teams are managed, and the project deliverables are physically created.
  4. Monitoring and Controlling: Simultaneously occurring with execution, this phase involves tracking progress against the baseline plan, reviewing performance metrics, and regulating progress via corrective actions when deviations occur.
  5. Closing: Finalizing all project activities, handing over the deliverables to the client, releasing project resources, and formally closing the project with a "lessons learned" review.

Work Breakdown Structure (WBS)

A Work Breakdown Structure (WBS) is a foundational project management tool. It is a hierarchical, deliverable-oriented decomposition of the total scope of work to be carried out by the project team. It breaks down a massive, complex project into smaller, highly manageable components called work packages, which can then be easily scheduled, cost-estimated, and assigned.

Scheduling Techniques

Accurate scheduling is the difference between a profitable engineering project and a catastrophic failure. Managers use several tools to visualize and calculate schedules.

Gantt Charts

A visual timeline bar chart that illustrates a project schedule. It clearly shows the start and finish dates of the various elements (work packages) of a project along a horizontal time axis, making it excellent for high-level stakeholder communication.

Critical Path Method (CPM)

A deterministic scheduling method that assumes task durations are known with certainty. It uses fixed time estimates for each activity.
  • Critical Path: The longest continuous sequence of activities through the network diagram. It determines the absolutely shortest possible duration to complete the entire project.
  • Slack (Float): The amount of time an activity can be delayed without delaying the subsequent activity (Free Float) or the final project completion date (Total Float). Activities on the Critical Path always have zero slack.

Program Evaluation and Review Technique (PERT)

A probabilistic scheduling method designed to handle uncertainty in task durations, commonly used in research and development or highly innovative engineering projects. It uses three distinct time estimates for each activity:
  • Optimistic time (tot_o): The minimum possible time to perform the activity, assuming everything goes perfectly and no risks occur.
  • Most likely time (tmt_m): The best, most realistic estimate of the time required to perform the activity under normal conditions.
  • Pessimistic time (tpt_p): The maximum possible time required to perform the activity, assuming almost everything goes wrong (excluding major catastrophes or acts of God).

PERT Expected Time ($t_e$)

$$ t_e = \frac{t_o + 4t_m + t_p}{6} $$

PERT Standard Deviation (\sigma)

$$ \sigma = \frac{t_p - t_o}{6} $$

Interactive PERT Chart

4233540
AStart
BDesign
CPermits
DProcure
ESite Prep
FBuild
GFinish

Click on any node in the network diagram above to view detailed scheduling information (ES, EF, LS, LF, and Slack).

CPM Network Diagram

Duration: 12 days

Activity Durations

Adays
Bdays
Cdays
Ddays
Edays

ES: Earliest Start

EF: Earliest Finish

LS: Latest Start

LF: Latest Finish

SL: Slack (Float)

START
ES:0
D:3
EF:3
Activity A
LS:4
SL:4
LF:7
ES:0
D:4
EF:4
Activity B
LS:0
SL:0
LF:4
ES:3
D:2
EF:5
Activity C
LS:7
SL:4
LF:9
ES:4
D:5
EF:9
Activity D
LS:4
SL:0
LF:9
ES:9
D:3
EF:12
Activity E
LS:9
SL:0
LF:12
END

Critical Chain Project Management (CCPM)

Developed by Eliyahu M. Goldratt, CCPM is an alternative to traditional CPM. While CPM focuses strictly on strict task dependencies and rigid deadlines, CCPM emphasizes managing the limited resources required to execute those tasks and the human psychological factors that cause delays.
  • Parkinson's Law: The observation that "work expands so as to fill the time available for its completion." CCPM aggressively cuts individual task time estimates by 50% to prevent workers from wasting time.
  • Student Syndrome: The tendency of people to wait until the absolute last possible minute to begin a task.
  • Project Buffers: Because individual task estimates are slashed, CCPM aggregates all that removed "safety time" into a single, massive "Project Buffer" at the very end of the schedule. Managers strictly monitor the consumption of this collective buffer rather than agonizing over individual task delays.

Resource Management

Schedules generated by CPM or PERT often ignore the physical reality of resource availability. A schedule might require 5 cranes on a Tuesday, but the contractor only owns 3.
  • Resource Leveling: Adjusting the start and finish dates of activities based strictly on resource constraints (e.g., delaying non-critical tasks because the necessary crane is currently occupied). This often results in extending the overall project duration beyond the original critical path.
  • Resource Smoothing: Reallocating resources within the available slack (float) of non-critical activities to create a more even, predictable daily demand for resources, without extending the final project deadline.

Project Risk Management

Engineering projects are inherently risky. A proactive risk management process is required to identify and handle uncertainties before they derail the project.
  1. Risk Identification: Systematically brainstorming potential events (weather delays, supplier bankruptcy, design flaws) that could negatively impact the project.
  2. Risk Assessment: Analyzing both the probability of the risk occurring and the severity of its impact (cost or schedule delay) using a Risk Matrix.
  3. Risk Response Planning: Developing strategies to handle high-priority risks: Avoid (change the plan completely), Transfer (buy insurance or shift liability in the contract), Mitigate (take early action to reduce the probability or impact), or Accept (set aside a contingency budget to absorb the blow).
  4. Risk Monitoring: Continuously tracking identified risks and identifying new ones throughout the project execution phase.

Project Crashing

When a project falls behind schedule, managers may use crashing, a schedule compression technique. Crashing involves shortening the project duration for the least incremental cost by adding resources to activities on the critical path (e.g., approving overtime, hiring temporary staff, or paying for expedited shipping).

Crash Cost per Unit Time

To determine which critical path activities to crash first, managers calculate the cost to shorten an activity by one unit of time (e.g., one day) and select the cheapest option.

Crash Cost per Time Unit

$$ \text{Crash Cost per Time Unit} = \frac{\text{Crash Cost} - \text{Normal Cost}}{\text{Normal Time} - \text{Crash Time}} $$

Earned Value Analysis (EVA)

EVA is an advanced, industry-standard method of measuring project performance and progress. It provides a highly objective view by combining measurements of scope, schedule, and cost into a single integrated quantitative system.

Key EVA Metrics

EVA relies on three core data points taken at a specific moment in time:
  • Planned Value (PV): The authorized budget assigned to the scheduled work that should have been accomplished by this date. (Also called Budgeted Cost of Work Scheduled - BCWS).
  • Earned Value (EV): The measure of work actually performed, expressed in terms of the budget originally authorized for that work. (Also called Budgeted Cost of Work Performed - BCWP).
  • Actual Cost (AC): The total realized cost actually incurred for the work performed to date. (Also called Actual Cost of Work Performed - ACWP).

Schedule Performance Index (SPI)

$$ \text{SPI} = \frac{\text{EV}}{\text{PV}} $$

Note

Interpretation: If SPI<1\text{SPI} < 1, the project is behind schedule. If SPI>1\text{SPI} > 1, the project is ahead of schedule.

Cost Performance Index (CPI)

$$ \text{CPI} = \frac{\text{EV}}{\text{AC}} $$

Note

Interpretation: If CPI<1\text{CPI} < 1, the project is over budget. If CPI>1\text{CPI} > 1, the project is under budget.

Agile Project Management

While traditional engineering projects (like bridge construction) follow a sequential, "Waterfall" methodology, many modern projects, particularly those involving software or complex systems integration, utilize Agile Project Management.

Core Principles of Agile

Agile is an iterative approach that focuses on continuous releases and incorporating customer feedback with every iteration.
  • Iterative Development: The project is broken down into small, manageable chunks called iterations or "sprints" (usually 1-4 weeks).
  • Flexibility and Adaptability: Requirements and solutions evolve through collaboration between self-organizing cross-functional teams. Changes are welcomed, even late in development.
  • Customer Collaboration: The customer or client is continuously involved in the development process, reviewing and providing feedback on each iteration.
  • Working Deliverables: The primary measure of progress is a functional product or deliverable piece of work at the end of each sprint.

Scrum Framework

Scrum is the most widely used Agile framework. It involves specific roles, artifacts, and ceremonies.
  • Roles: Scrum Master (facilitates the process), Product Owner (represents the stakeholders and prioritizes work), and Development Team (the cross-functional team doing the work).
  • Artifacts: Product Backlog (prioritized list of everything needed in the product), Sprint Backlog (the work selected for the current sprint), and Increment (the sum of all completed backlog items).
  • Ceremonies: Sprint Planning (planning the work for the upcoming sprint), Daily Scrum (short daily meeting to discuss progress and blockers), Sprint Review (demonstrating the completed work), and Sprint Retrospective (reflecting on the sprint and identifying improvements).

Note

Waterfall vs. Agile: The "Waterfall" methodology (sequential, rigid phases like Requirements →\rightarrow Design →\rightarrow Implementation →\rightarrow Testing) is still heavily preferred in civil and construction engineering due to the physical impossibility of changing foundational designs mid-construction. However, Agile is increasingly used in the design phases of civil engineering and in the development of engineering software.
Key Takeaways
  • Engineering managers choose between Traditional (Waterfall) methods for physical projects with stable requirements and Agile methods for iterative, software/R&D environments.
  • A project is a temporary endeavor with distinct phases: Initiation, Planning, Execution, Monitoring/Controlling, and Closing.
  • The Work Breakdown Structure (WBS) is a critical tool for hierarchically decomposing project scope into manageable work packages.
  • Scheduling techniques like CPM and PERT determine the Critical Path, while Resource Leveling/Smoothing ensure those schedules are actually achievable with physical constraints.
  • Proactive Risk Management (Identify, Assess, Mitigate/Transfer) and Crashing (compressing the schedule via critical path resource injection) are vital for overcoming unexpected hurdles.
  • Earned Value Analysis (EVA) provides an objective, integrated measure of project health by comparing Planned Value (PV), Earned Value (EV), and Actual Cost (AC) to generate Schedule (SPI) and Cost (CPI) performance indices.
PreviousControlling - Theory & Concepts
Quiz Me
NextOperations and Production Management - Theory & Concepts