Scheduling, cost, and quality are the three legs of the classic triple constraint, and PM4030 gives students the quantitative tools to actually manage them — not just discuss them conceptually. Every technique in this course exists to answer one question: are we on track, and if not, by how much?
Critical path method and schedule development
PM4030 teaches the critical path method (CPM): sequencing activities, estimating durations, and identifying the longest path through the network diagram — the sequence of dependent tasks that determines the minimum possible project duration. Any delay on the critical path delays the whole project; delays on non-critical paths simply consume float (slack) without affecting the end date, unless the float runs out. Students practice building network diagrams, calculating early/late start and finish dates, and identifying float for every activity.
Earned value management and cost of quality
Earned value management (EVM) is the course's central cost-and-schedule integration tool: by comparing planned value (PV), earned value (EV), and actual cost (AC), a project manager can calculate schedule variance (SV), cost variance (CV), and performance indexes (SPI, CPI) that reveal whether a project is ahead or behind, and under or over budget — using objective numbers instead of gut feeling. Quality management is taught alongside cost through the cost of quality framework: prevention and appraisal costs (the cost of doing it right) versus internal and external failure costs (the cost of doing it wrong), reinforcing that investing in quality upfront is nearly always cheaper than fixing defects later.
Key topics in PM4030
- Network diagrams: activity sequencing, dependencies (finish-to-start, start-to-start, etc.), and lead/lag
- Critical path method: forward pass, backward pass, float/slack calculation, and identifying the critical path
- Schedule compression: crashing (adding resources) vs. fast-tracking (parallel activities) and their trade-offs
- Cost estimating techniques: analogous, parametric, and bottom-up estimating
- Earned value management: PV, EV, AC, SV, CV, SPI, CPI, and estimate at completion (EAC)
- Cost of quality: prevention, appraisal, internal failure, and external failure costs
- Quality control tools: control charts, Pareto analysis, and cause-and-effect diagrams
Working on a CPM network diagram or an EVM analysis?
Our project management experts build PM4030-level coursework with accurate critical-path and earned-value calculations.
Worked example: reading an EVM status report
- Planned Value (PV): $50,000 of work was scheduled to be complete by today
- Earned Value (EV): $42,000 worth of work has actually been completed
- Actual Cost (AC): $48,000 has been spent to produce that $42,000 of earned value
- Schedule Variance (SV) = EV − PV = −$8,000 — the project is behind schedule
- Cost Variance (CV) = EV − AC = −$6,000 — the project is over budget
- Interpretation: Both SPI (0.84) and CPI (0.875) are below 1.0, signaling the project is both late and over budget — a corrective action plan is needed on both fronts
Get Help With PM4030
CPM network diagrams, EVM calculations, cost-of-quality analyses — done with the correct formulas.
Place Your OrderView All ServicesRelated courses
Frequently asked questions
Both are efficiency indexes derived from earned value, but they measure different dimensions of performance. The Schedule Performance Index (SPI = EV / PV) measures schedule efficiency — an SPI of 1.0 means the project is exactly on schedule, below 1.0 means less work has been completed than planned (behind schedule), and above 1.0 means ahead of schedule. The Cost Performance Index (CPI = EV / AC) measures cost efficiency — an CPI of 1.0 means the project is spending exactly what was budgeted for the work completed, below 1.0 means it is costing more than planned to produce that work (over budget), and above 1.0 means under budget. A project can be ahead of schedule but over budget (SPI above 1.0, CPI below 1.0) if the team is paying for overtime or extra resources to accelerate — which is exactly the kind of trade-off PM4030's EVM exercises are designed to surface and quantify.
Float, also called slack, is the amount of time an activity can be delayed without delaying the project's overall end date. Activities on the critical path have zero float by definition — any delay to a critical path activity delays the entire project, which is why it is called "critical." Activities not on the critical path have positive float, calculated as the difference between their late start (or finish) and early start (or finish) dates from the forward and backward pass. Understanding float matters for resource allocation: a project manager under a tight deadline can often pull resources from an activity with generous float and apply them to a critical-path activity without any schedule risk, since delaying the non-critical activity within its float doesn't change the project end date.