Basics of Project Management is a formula- and framework-heavy General Studies section tested in ESE Paper I. This module spans Project Lifecycle and Initiation (PMBOK phases, project charter, triple constraint), Scope Management and WBS (scope processes, work breakdown structure, scope creep), Project Scheduling (Gantt charts, CPM, PERT, schedule compression), Cost Management and Earned Value Analysis (cost estimation, EVA metrics), Project Risk Management (risk processes, response strategies), and Quality Management and Project Teams (quality tools, organisation structures, Tuckman's model) — with every definition, formula, and standard framework carried over, plus worked examples and diagrams for each topic.
After studying this chapter you will be able to:
Project Management complements the technical General Studies subjects by testing the managerial and organisational skills engineers need to deliver projects — schedule, cost, and quality control apply across every civil engineering discipline. Once you've worked through the chapters below, head to the Project Management hub page to generate practice tests, or explore Study Material for other subjects.
A project is a temporary endeavour to create a unique product, service, or result. Project management applies knowledge, skills, tools, and techniques to meet project requirements within scope, time, cost, and quality constraints.
| Aspect | Project | Operations |
|---|---|---|
| Duration | Temporary; defined start and end | Ongoing; continuous |
| Output | Unique product/result | Repetitive products/services |
| Resources | Assembled and disbanded | Permanent workforce |
| Goal | Achieve objectives and close | Sustain the business |
The Project Charter is a formal document authorising the project and the project manager's authority. It contains project purpose, objectives, scope, milestones, budget estimate, stakeholders, and risks, and is issued by the project sponsor or initiating entity.
| Stakeholder | Role |
|---|---|
| Project Sponsor | Champions project; provides funding; resolves escalated issues |
| Project Manager | Leads team; responsible for deliverables, budget, schedule |
| Project Team | Executes work; provides expertise |
| Client/Customer | Defines requirements; accepts deliverables |
| PMO | Project Management Office — sets standards, provides oversight |
Initiation → Planning → Executing → Monitoring & Controlling → Closing
Scope, Time, Cost (Quality at centre)
Formally authorises project; issued by sponsor
Project Management Office — sets standards, oversight
Given: A company builds a new factory (one-time effort with a defined end date), then begins ongoing manufacturing in it. Which activity is the "project," and which is "operations"?
Solution: Building the factory is temporary with a defined start and end — a project. Ongoing manufacturing is continuous, repetitive work sustaining the business — operations.
Answer: Factory construction = project; ongoing manufacturing = operations.
Given: A project manager is tracking actual progress against the baseline schedule and issuing performance reports. Which PMBOK lifecycle phase is this?
Solution: Tracking performance and reporting against a baseline is the defining activity of the Monitoring & Controlling phase, distinct from Executing (performing the work itself).
Answer: Monitoring & Controlling.
Given: A client demands the project scope be expanded midway through execution, but the deadline and budget must remain unchanged. What does the triple constraint predict will happen?
Solution: The triple constraint states that scope, time, and cost are interlinked — increasing scope while holding time and cost fixed will almost always compress quality or require unrealistic productivity, since one side of the triangle cannot expand without affecting the others.
Answer: Quality will likely suffer, since scope increased without a corresponding increase in time or cost.
Fig. 1.1 — The five PMBOK project lifecycle phases: Initiation, Planning, Executing, Monitoring & Controlling, and Closing.
Scope management ensures the project includes all — and only — the work required to complete the project successfully. Scope creep (uncontrolled expansion of scope) is a common cause of project failure.
| Type | Description |
|---|---|
| Functional requirements | What the system/product must do |
| Non-functional requirements | Performance, reliability, security, usability standards |
| Business requirements | Higher-level needs of the organisation |
| Stakeholder requirements | Needs and expectations of specific stakeholders |
WBS must capture 100% of project work
Deliverable-oriented, not activity-oriented
Uncontrolled scope expansion; no formal approval
Extra features added without client request
Given: A project manager creates a WBS but omits a minor administrative task, assuming it's "too small to matter." Does this violate the 100% rule?
Solution: Yes. The 100% rule requires the WBS to capture 100% of project work, however small. Omitting any task — even a minor one — means that work exists outside the scope baseline and won't be tracked, budgeted, or scheduled.
Answer: Yes, this violates the 100% rule.
Given: A developer adds an extra unrequested feature to impress the client, without any change request. Is this scope creep or gold plating?
Solution: Gold plating specifically refers to adding extra features not in scope without a client request, distinct from scope creep, which is uncontrolled scope expansion typically driven by external pressure or unmanaged change requests.
Answer: Gold plating.
Given: A client specifies that a web application must load within 2 seconds under peak load. What type of requirement is this?
Solution: This describes a performance standard rather than a specific function the system performs — it is a non-functional requirement.
Answer: Non-functional requirement.
Fig. 2.1 — A Work Breakdown Structure: hierarchical decomposition from Project → Deliverables → Work Packages.
Project scheduling defines the sequence and timing of project activities. Gantt charts, CPM, and PERT are the primary tools used to plan and track schedules.
PERT is suited for research/development projects where activity durations are uncertain, using three time estimates: \(t_o\) = optimistic time, \(t_m\) = most likely time, \(t_p\) = pessimistic time.
| Technique | Method | Trade-off |
|---|---|---|
| Crashing | Add resources to critical activities | Higher cost |
| Fast Tracking | Overlap activities originally planned in sequence | Higher risk |
| Resource levelling | Adjust schedule to balance resource use (may extend duration) | Extends duration |
Schedule baseline is the approved version of the project schedule. Schedule variance \(SV = EV - PV\) (negative = behind schedule); schedule performance index \(SPI = \dfrac{EV}{PV}\) (\(<1\) = behind schedule).
\(t_e = \dfrac{t_o + 4t_m + t_p}{6}\)
\(\sigma^2 = [\dfrac{t_p - t_o}{6}]^2\)
\(LS - ES = LF - EF\)
\(\dfrac{\text{Crash Cost}-\text{Normal Cost}}{\text{Normal Dur}-\text{Crash Dur}}\)
Given: An activity has \(t_o = 4\) days, \(t_m = 6\) days, \(t_p = 14\) days. Find the expected time and variance.
Solution: \(t_e = \dfrac{4 + 4(6) + 14}{6} = \dfrac{4+24+14}{6} = \dfrac{42}{6} = 7\) days. \(\sigma^2 = [\dfrac{14-4}{6}]^2 = (\dfrac{10}{6})^2 = 2.78\).
Answer: \(t_e = 7\) days; \(\sigma^2 \approx 2.78\).
Given: An activity has Early Start (ES) = 5, Late Start (LS) = 9. Find its total float.
Solution: Total Float \(= LS - ES = 9 - 5 = 4\) days.
Answer: 4 days (non-critical, since float \(> 0\)).
Given: A project manager needs to shorten the schedule but has no budget for additional resources. Which technique should be used, and what is the trade-off?
Solution: Fast tracking overlaps activities originally planned sequentially, shortening the schedule without extra cost — but it increases risk, since work proceeds based on incomplete predecessor information.
Answer: Fast tracking; trade-off is increased risk.
Fig. 3.1 — A CPM network: the critical path (A→B→D→E) is the longest path with zero float; the alternate path has slack.
Cost management involves planning, estimating, budgeting, and controlling costs. Earned Value Analysis (EVA) is the most powerful technique for measuring project performance against both schedule and budget simultaneously.
| Technique | Accuracy | When Used |
|---|---|---|
| Analogous estimating | Low (±25–50%) | Early stages; based on similar past projects |
| Parametric estimating | Medium (±10–25%) | Statistical relationship between variables (e.g. cost/unit) |
| Bottom-up estimating | High (±5–10%) | Detailed WBS available; sum of individual work packages |
| Three-point (PERT) | High | Uncertainty in estimates; uses optimistic/likely/pessimistic |
| Term | Definition |
|---|---|
| PV (Planned Value) | Budgeted cost of work scheduled (BCWS) — what was planned to be spent by now |
| EV (Earned Value) | Budgeted cost of work performed (BCWP) — the value of work actually done |
| AC (Actual Cost) | Actual cost of work performed (ACWP) — what was actually spent |
| BAC | Budget at Completion — total approved project budget |
| Cost Type | Description |
|---|---|
| Direct costs | Directly attributable to project (labour, materials, equipment) |
| Indirect costs | Overhead shared among projects (rent, utilities, admin) |
| Fixed costs | Do not vary with output (equipment hire, permits) |
| Variable costs | Vary with work output (materials consumed, hourly labour) |
| Sunk costs | Past expenditure that cannot be recovered — irrelevant to future decisions |
| Contingency reserve | Budget for known unknowns (identified risks) |
| Management reserve | Budget for unknown unknowns (unforeseeable risks) |
\(CV = EV-AC\); \(SV = EV-PV\)
\(CPI = \dfrac{EV}{AC}\); \(SPI = \dfrac{EV}{PV}\)
\(EAC = \dfrac{BAC}{CPI}\)
\(ETC = EAC-AC\); \(VAC = BAC-EAC\)
Given: A project has \(PV = 100{,}000\), \(EV = 90{,}000\), \(AC = 95{,}000\). Compute CPI and SPI, and interpret.
Solution: \(CPI = \dfrac{EV}{AC} = \dfrac{90{,}000}{95}{,}000 = 0.947\) (over budget, since \(<1\)). \(SPI = \dfrac{EV}{PV} = \dfrac{90{,}000}{100}{,}000 = 0.9\) (behind schedule, since \(<1\)).
Answer: \(CPI \approx 0.947\) (over budget); \(SPI = 0.9\) (behind schedule).
Given: A project has \(BAC = 500{,}000\) and \(CPI = 0.8\). Estimate the cost at completion.
Solution: \(EAC = \dfrac{BAC}{CPI} = \dfrac{500{,}000}{0.8} = 625{,}000\).
Answer: \(EAC = 625{,}000\) — the project is forecast to cost more than the original budget.
Given: A company spent ₹2 lakh on a feasibility study for a project that was subsequently cancelled. Should this cost influence the decision to start a new, unrelated project?
Solution: The ₹2 lakh is a sunk cost — past expenditure that cannot be recovered. Sunk costs are irrelevant to future decisions and should not influence whether to start the new project.
Answer: No — it is a sunk cost and should be ignored in the new decision.
Fig. 4.1 — Earned Value Analysis: comparing Planned Value, Earned Value, and Actual Cost curves to derive CV and SV.
Risk is an uncertain event or condition that, if it occurs, has a positive or negative effect on project objectives. Risk management proactively identifies, analyses, and responds to risks.
| Strategy (Threats) | Description | Example |
|---|---|---|
| Avoid | Eliminate threat by eliminating cause | Change project scope to exclude risky work |
| Transfer | Shift risk to third party | Insurance, contract with penalty clause |
| Mitigate | Reduce probability or impact | More testing, redundant systems, training |
| Accept | Acknowledge risk; no action (active = contingency; passive = accept consequence) | Small low-probability risks |
The Risk Register is a living document containing all identified risks, their causes, probability, impact, owner, and response, updated throughout the project lifecycle.
| Impact → | Low | Medium | High |
|---|---|---|---|
| High probability | Medium | High | Critical |
| Medium probability | Low | Medium | High |
| Low probability | Low | Low | Medium |
Probability × Impact
Avoid, Transfer, Mitigate, Accept
Exploit, Share, Enhance, Accept
Monte Carlo simulation, decision trees
Given: A construction project faces a risk of severe weather delays. The project team purchases weather-delay insurance to cover the potential cost. Which risk response strategy is this?
Solution: Purchasing insurance shifts the financial impact of the risk to a third party (the insurer), which is the defining feature of the Transfer strategy.
Answer: Transfer.
Given: A project team redesigns a bridge to eliminate a risky construction technique entirely, versus another team that adds extra safety inspections to reduce the same risk's likelihood. Which team is using "Avoid," and which is using "Mitigate"?
Solution: Eliminating the risky technique entirely removes the cause of the risk — this is Avoid. Adding extra inspections reduces the probability of the risk occurring without eliminating its cause — this is Mitigate.
Answer: Redesign team = Avoid; inspection team = Mitigate.
Given: A risk has high probability of occurring but only low impact if it does. How should it be classified on the standard probability × impact matrix?
Solution: Per the matrix, high probability combined with low impact yields a "Medium" classification — not the highest-priority "Critical" category, which requires both high probability and high impact.
Answer: Medium priority.
Fig. 5.1 — Probability × Impact matrix: risk priority rises from Low (top-left) to Critical (bottom-right).
Quality management ensures the project satisfies the needs for which it was undertaken. It encompasses quality planning, quality assurance, and quality control across all project processes and deliverables.
| Term | Definition |
|---|---|
| Quality | Degree to which deliverables meet specified requirements |
| Grade | Category of products with same functional use but different requirements (low grade ≠ low quality) |
| Quality Assurance (QA) | Audit processes to ensure quality standards are followed (process-focused) |
| Quality Control (QC) | Monitor specific project results to check they meet quality standards (product-focused) |
| Cost of Quality (CoQ) | Cost of conformance (prevention + appraisal) + cost of non-conformance (internal + external failures) |
| Tool | Use |
|---|---|
| Pareto chart | 80/20 rule — 80% of defects from 20% of causes; prioritise improvement |
| Cause & Effect (Ishikawa/fishbone) | Identify root causes of defects (6 Ms: Man, Machine, Method, Material, Measurement, Mother Nature) |
| Control chart | Statistical process control; identify special vs. common cause variation |
| Scatter diagram | Shows relationship between two variables |
| Histogram | Distribution of defects by category or time |
| Flowchart | Process mapping to identify improvement opportunities |
| Checklist | Tally defects by type for data collection |
| Structure | PM Authority | Advantages | Disadvantages |
|---|---|---|---|
| Functional | Little to none | Technical expertise; career path | Poor PM control; slow decisions; "silo" mentality |
| Projectised | High to total | Full PM control; fast decisions; team loyalty | Inefficient resource use; loss of technical home |
| Matrix (Weak) | Limited | Better resource sharing | Dual reporting causes conflict |
| Matrix (Balanced) | Shared PM/Functional | Balance of control and expertise | Complex; potential for conflict |
| Matrix (Strong) | High | PM control; resource efficiency | Dual reporting; overhead |
Tuckman's Model: (1) Forming — team comes together, polite, uncertain, PM provides direction; (2) Storming — conflict over roles and approaches, PM facilitates resolution; (3) Norming — team establishes norms, cohesion builds, PM steps back; (4) Performing — high performance, team self-organises, PM empowers; (5) Adjourning — project ends, team disbands, PM recognises contributions.
| Technique | Description | Best Use |
|---|---|---|
| Collaborate / Problem-solve | Win-win; work through conflict to find solution both parties accept | Best long-term resolution |
| Compromise / Reconcile | Give-and-take; both parties concede something | Temporary or partial solution |
| Withdraw / Avoid | Postpone or retreat from conflict | Not currently important; more info needed |
| Smooth / Accommodate | Emphasise areas of agreement; downplay differences | Maintain harmony; minor issues |
| Force / Direct | One party imposes solution | Emergency; decisiveness needed |
QA = process audit (proactive); QC = product check (reactive)
80% of defects from 20% of causes
Forming → Storming → Norming → Performing → Adjourning
Best: Collaborate (win-win); Worst: Force (win-lose)
Given: A company audits its testing procedures to confirm they follow the documented quality process, separately from inspecting a specific finished product for defects. Which activity is QA, and which is QC?
Solution: Auditing the process itself (to ensure standards are followed) is Quality Assurance; inspecting the specific finished product for defects is Quality Control.
Answer: Process audit = QA; product inspection = QC.
Given: A quality team finds that 4 out of 20 defect categories account for the vast majority of reported defects. Which quality tool and principle does this illustrate?
Solution: This is the Pareto principle (80/20 rule), visualised using a Pareto chart — a small number of causes (here, 4 of 20 = 20%) account for the majority of the effect (defects).
Answer: Pareto chart / Pareto principle.
Given: A newly formed project team is experiencing friction over roles and differing approaches to the work, requiring the project manager to actively mediate. Which Tuckman stage is this?
Solution: Conflict over roles and approaches, requiring active PM facilitation, is the defining characteristic of the Storming stage, which follows the initial polite uncertainty of Forming.
Answer: Storming.
Fig. 6.1 — Tuckman's five stages of team development: Forming → Storming → Norming → Performing → Adjourning.
Initiation → Planning → Executing → Monitoring & Controlling → Closing
Scope, Time, Cost (Quality at centre)
WBS must capture 100% of project work
Deliverable-oriented (not activity-oriented)
\(t_e = \dfrac{t_o + 4t_m + t_p}{6}\); \(\sigma^2 = [\dfrac{t_p-t_o}{6}]^2\)
CPM = deterministic (1 estimate); PERT = probabilistic (3 estimates)
Overlap sequential activities; increases risk
Add resources to critical path; increases cost
\(CPI = \dfrac{EV}{AC}\); \(<1\) = over budget
\(SPI = \dfrac{EV}{PV}\); \(<1\) = behind schedule
\(CV = EV-AC\); \(SV = EV-PV\); negative = bad
\(EAC = \dfrac{BAC}{CPI}\)
Eliminate threat by eliminating its cause
Insurance, contracts shift risk to third party
Reduce probability or impact of threat
Forming → Storming → Norming → Performing → Adjourning
Collaborate/Problem-solve (win-win)
QA = process audit (proactive); QC = product check (reactive)
80% of defects from 20% of causes
Uncontrolled scope expansion; major project risk
Past cost that cannot be recovered; irrelevant to future decisions
| Topic | Paper I Focus |
|---|---|
| Project Lifecycle | PMBOK phase identification; triple constraint reasoning |
| Scope & WBS | 100% rule and deliverable-orientation; scope creep vs gold plating |
| Scheduling | PERT expected-time/variance numericals; float computation; CPM vs PERT |
| Cost Management | EVA metric numericals (CPI, SPI, EAC); cost-type classification |
| Risk Management | Response-strategy matching (threats vs opportunities); probability × impact matrix |
| Quality & Teams | QA vs QC distinction; Tuckman stage identification; conflict-resolution ranking |
Q1. An activity has to = 3 days, tm = 5 days, tp = 13 days. Find its PERT expected time.
Q2. A project has PV = 80,000, EV = 72,000, AC = 76,000. Compute SPI.
Q3. A project has BAC = 400,000 and CPI = 1.25. Find the EAC.
Q4. A project team decides to insure against a risk rather than eliminate or reduce it. Which response strategy is this?
Q5. A team is newly formed and members are polite but uncertain about their roles. Which Tuckman stage is this?