PCC: Construction Technology and Project Management
UNIT 3 — PROJECT MANAGEMENT
Detailed Notes — Role of PM • Stakeholders • Project Types • Triple Constraint • Knowledge Areas • WBS •
Planning/Monitoring/Executing • Scheduling • Bar Charts • Networks • CPM • PERT • Cash Flow • Resource Levelling & Allocation •
Crashing • EVA • Construction Finance Decisions
3.1 Role of the Project Manager
A Project Manager (PM) is the individual formally accountable for planning, executing, monitoring, controlling and
closing a construction project so that it meets defined objectives of scope, time, cost and quality. The PM acts as the single
point of coordination between the owner, design team, contractors, and regulatory authorities.
Key Responsibilities
• Defining project objectives, scope and deliverables in consultation with the owner/client.
• Developing the project plan — schedule, budget, resource plan, quality plan and risk plan.
• Organising the project team and assigning roles and responsibilities.
• Coordinating between architects, structural/MEP consultants, contractors and vendors.
• Monitoring progress against baseline schedule and budget; taking corrective action on deviations.
• Managing procurement, tendering and contract administration.
• Ensuring compliance with safety norms, statutory regulations and quality standards.
• Risk identification, assessment and mitigation planning.
• Stakeholder communication and conflict/dispute resolution.
• Project closure — final inspection, handover, documentation and lessons learned.
Essential Skills of a PM
• Technical knowledge of construction methods and materials.
• Leadership and team-building ability.
• Negotiation and communication skills.
• Financial and contract management acumen.
• Decision-making under uncertainty and time pressure.
3.2 Stakeholders in a Construction Project
A stakeholder is any individual, group or organisation that can affect, be affected by, or perceive itself to be affected by a
project's decisions, activities or outcome.
Classification of Stakeholders
Category Examples Interest
Internal / Primary Owner/Client, Project Manager, Directly execute or fund the
Contractors, Consultants, Employees project
External / Secondary Government bodies, Local community, Indirectly affected —
Suppliers, Financial institutions, Media, regulation, environment,
NGOs funding
Key Stakeholder Roles
• Owner/Client — provides finance, defines requirements, gives approvals.
• Project Manager — coordinates and controls execution.
• Architect/Consultant — designs and certifies conformance to design intent.
• Contractor & Sub-contractors — execute construction work.
• Suppliers/Vendors — supply materials, plant and equipment.
• Regulatory bodies — approve plans, enforce codes and by-laws.
• End users/Community — affected by the project's operation and environmental impact.
Exam tip: Stakeholder analysis is usually plotted on a Power–Interest grid to decide the level of engagement (manage
closely, keep satisfied, keep informed, monitor).
3.3 Types of Projects — Similarities & Dissimilarities
Classification by Nature
• Residential projects — houses, apartments, townships.
• Commercial projects — offices, malls, hotels.
• Industrial projects — factories, warehouses, plants.
• Infrastructure projects — roads, bridges, dams, airports, railways.
• Institutional projects — schools, hospitals, government buildings.
Classification by Ownership
• Public projects — funded and executed by government departments/agencies for public use (e.g., government
roads, hospitals, dams); financed through public budgets/taxation.
• Private projects — funded and executed by private individuals/companies primarily for private use or profit (e.g.,
private residences, corporate offices, factories).
• Public-Private Partnership (PPP) projects — jointly developed by government and private entities, combining
public oversight with private capital/efficiency (e.g., toll roads, airports under BOT/BOOT/HAM models); risk
and revenue are shared as per the concession agreement.
Similarities Across Project Types
• All follow the generic project life cycle: Initiation → Planning → Execution → Monitoring & Control → Closure.
• All are constrained by the triple constraint of time, cost and scope/quality.
• All require stakeholder coordination, risk management and resource planning.
Dissimilarities
Aspect Building Projects Infrastructure Projects
Duration Generally shorter Longer, multi-year
Size Smaller footprint, single site Large scale, often spans multiple
sites/regions
Cost Relatively lower project cost Very high capital cost, large budgets
Complexity Moderate, repetitive elements High, often unique site conditions
Technology Conventional construction methods Advanced/specialised technology and
equipment
Location Urban/suburban, defined plot Often remote, varied terrain, spread over
large areas
Stakeholders Fewer — owner, contractor Many — government, public, multiple
agencies
Financing Private, often self-funded Public/PPP funded, phased disbursement
Risk profile Design & construction risk Environmental, land-acquisition, political
risk
3.4 Time, Scope and Money — The Triple Constraint
Every project is governed by the classic Triple Constraint (Project Management Triangle): Time, Cost (Money) and
Scope, with Quality often placed at the centre since a change in any one factor affects the others.
• Scope — the work content and deliverables that define what the project will produce.
• Time — the schedule/duration within which the scope must be delivered.
• Cost/Money — the budget allocated to deliver the scope within the given time.
Increasing scope without additional time or cost reduces quality; compressing time typically increases cost (see Crashing,
Section 3.13); reducing cost may require reducing scope or extending time. Effective project management balances these
three dimensions to meet the owner's objectives.
3.5 Knowledge Areas & Processes in Construction Projects
As per the PMBOK (Project Management Body of Knowledge) framework, project management is organised into
knowledge areas, each with associated processes grouped into five process groups.
Ten Knowledge Areas
1. Project Integration Management — coordinating all parts of the project.
2. Scope Management — defining and controlling what is/is not included.
3. Time (Schedule) Management — planning and controlling the schedule.
4. Cost Management — budgeting, estimating and controlling cost.
5. Quality Management — ensuring deliverables meet requirements.
6. Resource (Human Resource) Management — organising and managing the project team.
7. Communications Management — ensuring timely and appropriate information flow.
8. Risk Management — identifying, analysing and responding to risk.
9. Procurement Management — acquiring goods/services from outside the team.
10. Stakeholder Management — identifying and engaging stakeholders.
Five Process Groups
• Initiating — authorising the project or phase.
• Planning — establishing scope, objectives and course of action.
• Executing — completing the work defined in the plan.
• Monitoring & Controlling — tracking, reviewing and regulating progress.
• Closing — finalising all activities to formally close the project.
3.6 Work Breakdown Structure (WBS)
A Work Breakdown Structure is a hierarchical decomposition of the total scope of work into smaller, manageable
components called work packages. It follows the '100% rule' — the WBS includes 100% of the work defined by the
project scope.
Levels of a Typical Construction WBS
1. Level 0 — Project (e.g., Construction of a Residential Building)
2. Level 1 — Major phases (Substructure, Superstructure, Finishing, Services)
3. Level 2 — Deliverables/systems (Foundation, Columns, Slabs, Walls, Roofing, Plumbing, Electrical)
4. Level 3 — Work packages (Excavation, PCC, Reinforcement, Shuttering, Concreting, Curing)
Purpose of WBS
• Provides a basis for cost estimation and budgeting.
• Forms the basis for developing the project schedule (activities are derived from work packages).
• Assists in assigning responsibility to individuals/teams.
• Enables progress monitoring and earned value measurement.
Exam tip: A WBS answers 'what' work is to be done; it is NOT a schedule (which answers 'when') — this distinction is a
common exam question.
3.7 Planning, Monitoring and Executing
Planning
Planning involves deciding in advance what to do, how to do it, and who will do it. It includes defining activities,
sequencing them, estimating durations and resources, and preparing the budget and schedule baseline.
Executing
Execution is the phase where the planned work is physically carried out — mobilising resources, procuring materials, and
directing site operations in accordance with the plan and specifications.
Monitoring & Controlling
This involves continuously comparing actual progress (time, cost, quality) against the baseline plan, identifying
variances, and initiating corrective/preventive action. Tools used include progress reports, site inspections, S-curves and
Earned Value Analysis.
• Planning answers: What, How, When, Who.
• Executing answers: Doing the actual work.
• Monitoring answers: Are we on track? What corrective action is needed?
3.8 Planning, Sequencing and Scheduling
• Planning — identifying all activities required to complete the project scope (derived from the WBS).
• Sequencing — establishing the logical order of activities and their interdependencies (predecessor–successor
relationships: Finish-to-Start, Start-to-Start, Finish-to-Finish, Start-to-Finish).
• Scheduling — assigning time durations, start/finish dates and resources to sequenced activities to produce a time-
phased plan (Bar Chart / Network Diagram).
The sequence Planning → Sequencing → Scheduling → Resource allocation → Monitoring forms the backbone of
construction project time management.
3.9 Bar Charts (Gantt Charts)
A Bar Chart, also called a Gantt Chart, represents project activities as horizontal bars plotted against a time scale, where
the length of the bar indicates the duration of the activity.
Advantages
• Simple to prepare, read and understand — useful for communication with non-technical stakeholders.
• Clearly shows start and finish dates of each activity.
• Progress can be tracked by shading completed portions of bars.
Limitations
• Does not clearly show interdependencies between activities.
• Difficult to identify the critical path directly.
• Not easily updated for large, complex projects with many interrelated activities.
Exam tip: Bar charts are best suited for small/medium projects; CPM/PERT networks are preferred for large, complex
projects with many interdependent activities.
3.10 Networks (Network Diagrams)
A network diagram is a graphical representation of project activities and their logical sequence/interdependencies, using
nodes and arrows. Two conventions are used:
• Activity-on-Arrow (AOA) — activities are represented by arrows; nodes represent events (start/end points).
• Activity-on-Node (AON) / Precedence Diagramming Method (PDM) — activities are represented by
nodes/boxes; arrows show only the dependency/logic.
Basic Network Terms
• Event — a point in time marking the start or completion of an activity (used in AOA).
• Activity — a task consuming time and resources.
• Dummy activity — a zero-duration activity used in AOA to show logical dependency without consuming
resources.
• Path — a continuous chain of activities from start to end of the project.
• Critical Path — the longest path through the network; determines the minimum project duration.
3.11 Critical Path Method (CPM)
CPM is a deterministic network technique used for projects where activity durations are known/estimated with reasonable
certainty (typically repetitive construction work). It identifies the critical path — the sequence of activities that determines
the shortest possible project duration; any delay in a critical activity delays the whole project.
Key Terms
Term Meaning
EST Earliest Start Time of an activity
EFT Earliest Finish Time (EST + Duration)
LST Latest Start Time without delaying the project
LFT Latest Finish Time without delaying the project
Total Float LST − EST (or LFT − EFT); slack available without delaying the project
Free Float Delay possible without affecting the succeeding activity's earliest start
Procedure
1. Draw the network diagram from the activity list and logical dependencies.
2. Perform Forward Pass — compute EST and EFT for each activity (start = 0, moving left to right, taking the
maximum EFT of predecessors).
3. Perform Backward Pass — compute LFT and LST (start from project end, moving right to left, taking the
minimum LST of successors).
4. Calculate Total Float for each activity = LST − EST.
5. Identify the Critical Path — activities with zero float; this path determines the project duration.
Worked Example — CPM
An activity B has EST = 4 days and duration = 6 days, so EFT = 4 + 6 = 10 days. If its LFT (fixed by the backward pass) =
13 days, then LST = LFT − Duration = 13 − 6 = 7 days.
Total Float = LST − EST = 7 − 4 = 3 days. Since float ≠ 0, activity B is NOT on the critical path; it can be delayed by up to 3
days without affecting the project's completion date.
3.12 Programme Evaluation and Review Technique (PERT)
PERT is a probabilistic network technique used when activity durations are uncertain (research, novel, or non-repetitive
projects). It uses three time estimates for each activity:
• Optimistic time (to) — shortest possible duration under ideal conditions.
• Most likely time (tm) — duration under normal conditions.
• Pessimistic time (tp) — longest duration under adverse conditions.
Formulae
Expected time: te = (to + 4tm + tp) / 6
Standard deviation: σ = (tp − to) / 6
Variance: σ² = [(tp − to) / 6]²
Worked Example — PERT
For an activity: Optimistic time (to) = 4 days, Most likely time (tm) = 6 days, Pessimistic time (tp) = 14 days.
Expected time: te = (4 + 4×6 + 14) / 6 = (4 + 24 + 14) / 6 = 42 / 6 = 7 days.
Standard deviation: σ = (14 − 4) / 6 = 10 / 6 = 1.67 days. So the activity is expected to take 7 days, with a spread of ±1.67
days.
CPM vs PERT
Basis CPM PERT
Nature Deterministic (single time estimate) Probabilistic (three time estimates)
Focus Cost–time trade-off / activity-oriented Time / event-oriented, handles uncertainty
Suitable for Repetitive projects (construction, Non-repetitive, R&D, novel projects
manufacturing)
Crashing Applicable Not typically applied
3.13 Cash Flow Diagram
A cash flow diagram/curve represents the cumulative inflow (receipts/payments from client) and outflow (expenditure on
labour, material, plant) of money over the project duration. In construction, the cumulative expenditure curve typically
follows an 'S-curve' shape — slow expenditure at the start, rapid expenditure during peak execution, and tapering again
near completion.
Uses of Cash Flow / S-Curve
• Forecasting the contractor's working-capital requirement at any stage of the project.
• Planning of interim/progress billing and payment schedules.
• Comparing planned versus actual expenditure for cost control.
• Assisting in financial decision-making for arranging credit or loans.
Exam tip: The 'S-curve' name comes from the characteristic S-shape of cumulative cost/progress plotted against time — a
frequently sketched diagram in exams.
3.14 Resource Levelling and Resource Allocation
Resource Allocation (Resource Loading)
The process of assigning available resources (labour, equipment, material, money) to scheduled activities. It may reveal
periods of resource over-allocation (demand exceeding availability).
Resource Levelling
A technique used to resolve resource over-allocation by adjusting activity start/finish dates (within available float) so that
resource demand does not exceed supply, resulting in a smoother, more uniform resource-usage profile over the project
duration. Levelling may extend the project duration if float is insufficient to absorb the adjustment.
Objectives
• Avoid sudden peaks and troughs in resource demand.
• Ensure resources (especially labour and equipment) are used efficiently without idle time or shortage.
• Minimise cost associated with mobilising/demobilising resources repeatedly.
3.15 Crashing of a Project
Crashing is a schedule-compression technique in which the duration of one or more critical activities is deliberately
reduced (by adding resources, overtime, or better technology) to shorten the overall project duration, usually at an
increased direct cost.
Key Terms
• Normal Time & Normal Cost — duration/cost under normal working conditions.
• Crash Time & Crash Cost — the minimum possible duration and the corresponding (higher) cost.
• Cost Slope = (Crash Cost − Normal Cost) / (Normal Time − Crash Time) — the cost of reducing duration by one
unit of time.
Procedure
1. Identify the critical path in the normal network.
2. Select the critical activity with the lowest cost slope for crashing first.
3. Crash that activity by one time unit at a time; recompute the critical path (it may shift or a new path may become
critical).
4. Continue until further crashing is not possible or the increase in indirect-cost savings no longer offsets the
increase in direct cost — this gives the Optimum (Least-Cost) Duration.
Worked Example — Crashing
A critical activity has Normal Time = 10 days at Normal Cost ₹20,000, and Crash Time = 6 days at Crash Cost ₹32,000.
Cost Slope = (32,000 − 20,000) / (10 − 6) = 12,000 / 4 = ₹3,000 per day. So each day this activity is crashed adds ₹3,000 to
the direct cost — the activity with the lowest such slope on the critical path is crashed first.
Exam tip: Total project cost = Direct cost + Indirect cost. As duration is crashed, direct cost rises while indirect cost
(supervision, overheads) falls — the optimum duration lies where total cost is minimum.
3.16 Earned Value Analysis (EVA)
Earned Value Analysis is an integrated technique that combines scope, schedule and cost data to objectively measure
project performance and progress.
Core Parameters
Term Symbol Meaning
Planned Value PV (BCWS) Budgeted cost of work scheduled to date
Earned Value EV (BCWP) Budgeted cost of work actually performed to
date
Actual Cost AC (ACWP) Actual cost incurred for work performed to
date
Budget at Completion BAC Total budget for the project
Key Formulae
Cost Variance: CV = EV − AC (Positive = under budget)
Schedule Variance: SV = EV − PV (Positive = ahead of schedule)
Cost Performance Index: CPI = EV / AC
Schedule Performance Index: SPI = EV / PV
Estimate at Completion: EAC = BAC / CPI
Worked Example — EVA
For a project: PV = ₹5,00,000, EV = ₹4,50,000, AC = ₹5,20,000, BAC = ₹20,00,000.
CV = EV − AC = 4,50,000 − 5,20,000 = −₹70,000 (over budget). SV = EV − PV = 4,50,000 − 5,00,000 = −₹50,000 (behind
schedule).
CPI = EV/AC = 4,50,000/5,20,000 = 0.87. SPI = EV/PV = 4,50,000/5,00,000 = 0.90. EAC = BAC/CPI = 20,00,000/0.87 ≈
₹22,99,000 — since CPI < 1, the project is expected to cost more than originally budgeted.
Exam tip: CPI/SPI > 1 → performing better than planned (efficient); CPI/SPI < 1 → over budget/behind schedule. This is a
very frequently asked numerical topic.
3.17 Construction Finances — Decision Making
Financial decision-making in construction relates to how project funds are planned, sourced, allocated and controlled to
ensure the project remains financially viable.
Key Aspects
• Sources of finance — owner's equity, bank loans, project finance, public funding, PPP models.
• Budgeting and cost estimation at various project stages (preliminary, detailed, definitive estimates).
• Cash flow forecasting — matching inflows (client payments/loan disbursement) with outflows (material, labour,
plant, overheads).
• Working capital management — ensuring liquidity to sustain ongoing operations.
• Investment appraisal techniques — Payback Period, Net Present Value (NPV), Internal Rate of Return (IRR),
Benefit-Cost Ratio (BCR) used to evaluate project viability.
• Risk-based financial decisions — contingency allowances, insurance, retention money, bank guarantees.
Sound financial decision-making ensures the project is completed within budget, protects the contractor's/owner's
liquidity, and provides a basis for go/no-go decisions at each project milestone.
Quick Revision Summary
Topic One-line takeaway
PM Role Single point of accountability for scope, time, cost, quality
Stakeholders Internal (direct) vs External (indirect) interest groups
Triple Constraint Time – Cost – Scope, balanced around Quality
WBS Hierarchical breakdown of scope into work packages (100% rule)
Bar Chart Simple time-scaled bars; weak on interdependencies
CPM Deterministic; critical path = zero float; used for known durations
PERT Probabilistic; te = (to+4tm+tp)/6; used for uncertain durations
Resource Levelling Smooths resource demand within available float
Crashing Reduces duration by increasing direct cost on critical activities
EVA CV=EV−AC, SV=EV−PV, CPI=EV/AC, SPI=EV/PV