Project management

In short

Project management is the application of knowledge, skills, tools and techniques to a temporary, unique undertaking so that it is delivered within scope, time, cost and quality limits. It matters because every organisation runs change through projects - a plant expansion, an ERP rollout, a new branch, a product launch - and most overruns are planning failures, not technical ones. In BBA/BMS Operations papers it carries a full question (life cycle, WBS, CPM/PERT networks, crashing, Gantt), and in placements it appears as network problems in aptitude rounds and as "tell me how you would plan this" in interviews for roles at L&T, Tata Projects, Infosys, TCS, Accenture, Capgemini and PMO teams across BFSI.

Explained

What a project is, and the triple constraint

• A project is temporary (defined start and end), unique in output, progressively elaborated and resource-constrained - unlike operations, which are repetitive and ongoing.
• The triple constraint (iron triangle): scope, time and cost, with quality at the centre. Tighten one and at least one other must give; this trade-off is the heart of most interview answers.
• A programme is a group of related projects managed together; a portfolio is the whole set of programmes and projects aligned to strategy.
• Project organisation structures: functional (PM has little authority), matrix (shared authority - weak, balanced or strong) and projectised (PM has full authority, resources dedicated).
• The global reference frameworks are PMBOK Guide (PMI), PRINCE2 and ISO 21500/21502 on project management guidance; PMI's PMP and CAPM are the certifications Indian employers ask for.

Project life cycle and processes

1. Initiation - identify need, feasibility study, stakeholder identification, project charter (authorises the project and names the PM).
2. Planning - scope statement, WBS, activity list, network and schedule, budget, risk register, quality plan, procurement plan, communication plan.
3. Execution - acquire and direct the team, do the work, manage vendors and quality.
4. Monitoring and control - track time, cost and scope; change control to stop scope creep; corrective action.
5. Closure - handover, final accounts, release of resources, lessons learned document.
6. Work Breakdown Structure (WBS): hierarchical decomposition of the deliverable into work packages small enough to estimate and assign; the 100% rule says the WBS must contain all the work and nothing more. A RACI chart (Responsible, Accountable, Consulted, Informed) assigns the work packages.
7. Risk management: identify, assess (probability × impact), respond (avoid, mitigate, transfer - typically through insurance or a fixed-price contract - or accept), monitor. Contingency reserve covers known risks; management reserve covers unknown ones.

Network techniques - CPM and PERT

• A network diagram shows activities and their dependencies. Activity-on-arrow needs dummy activities (zero duration) to show dependence without consuming time; activity-on-node (precedence diagram) is now standard.
• Forward pass gives Earliest Start/Finish (ES, EF); backward pass gives Latest Start/Finish (LS, LF).
• Total float = LS − ES = LF − EF. The critical path is the longest duration path through the network; its activities have zero float and any delay on them delays the project.
• Free float = ES of the following activity − EF of this activity; it can be used without disturbing any successor.
• CPM assumes single, deterministic durations - used in construction and repetitive work where times are known.
• PERT assumes probabilistic durations from three estimates (optimistic a, most likely m, pessimistic b), giving an expected time and a variance - used in R&D and new work.
• Gantt chart (bar chart): a time-scaled bar per activity; excellent for communication and progress tracking, but it does not show dependencies or float the way a network does.
• Crashing: shortening the project by adding resources to critical activities, starting with the lowest cost slope, until the extra direct cost exceeds the indirect/penalty saving - this gives the optimum (least total cost) duration.
• Resource levelling smooths resource use within the existing project duration using float; resource smoothing/allocation under a fixed resource limit may extend the duration.
• Limitations: estimates are only as good as the data; PERT's beta assumption and independence of paths are approximations; networks ignore learning effects and cash flow unless modelled separately.

Project cost and performance control

• Earned Value Management (EVM) measures progress in money: PV (planned value), EV (earned value), AC (actual cost). It is the standard answer to "how do you know a project is late and over budget at the same time?"
• Project appraisal for selection uses NPV, IRR and payback - the finance paper's tools applied to project choice.
• In India, large infrastructure projects are monitored through the PRAGATI platform and the Ministry of Statistics and Programme Implementation's flash reports on central sector projects of ₹150 crore and above; Gati Shakti is the national master plan for infrastructure coordination. Public procurement follows the General Financial Rules, 2017 and GeM; construction labour and safety are now governed by the four Labour Codes in force from 21 November 2025, which replaced the Factories Act, the BOCW Act and the other repealed statutes. Construction contracts commonly use FIDIC or CPWD/NHAI standard forms, with arbitration under the Arbitration and Conciliation Act.

Key points

• Project - temporary, unique, resource-constrained undertaking with a defined end.
• Triple constraint - scope, time, cost (quality at the centre); changing one forces a trade-off.
• Charter - document that authorises the project and empowers the project manager.
• WBS - decomposition into work packages; follows the 100% rule, basis of all estimates.
• Critical path - longest path; zero float; sets the minimum project duration.
• Total float - LS − ES; delay available without delaying the project.
• CPM vs PERT - deterministic, cost-oriented vs probabilistic, time-oriented.
• PERT expected time - weighted average (a + 4m + b)/6, variance ((b − a)/6)².
• Crashing - compress the critical path cheapest-slope-first; trade direct cost against indirect cost.
• Resource levelling - use float to smooth manpower without extending the project.
• Scope creep - uncontrolled addition of work; controlled by formal change control.
• EVM - SV and CV in money; CPI/SPI below 1 means over budget/behind schedule.
• Closure - handover plus lessons learned; skipping it loses all organisational learning.

Formulas and examples

Example 1 - PERT: expected time, variance and probability A project has three activities in series on its only path:

• Expected project duration TE = 7 + 10 + 5 = 22 days.
• Variance = 2.78 + 4.00 + 1.00 = 7.78 → σp = √7.78 ≈ 2.79 days.
• Probability of finishing in 25 days: Z = (25 − 22)/2.79 ≈ 1.08 → from the normal table, about 86%.
• Probability of finishing in 22 days = 50%, because TE is the mean - a standard exam trap.

Example 2 - Crashing to least total cost A project of 5 activities has a critical path A → B → C of 20 days. Indirect cost is ₹8,000 per day.

• Normal direct cost on this path = 50,000 + 70,000 + 40,000 = ₹1,60,000; indirect = 20 × 8,000 = ₹1,60,000 → total ₹3,20,000.
• Step 1: crash A by 2 days at ₹6,000/day = ₹12,000 extra direct; indirect saved = 2 × 8,000 = ₹16,000 → net saving ₹4,000. Duration 18 days, total cost = 1,72,000 + 1,44,000 = ₹3,16,000.
• Step 2: crash B by 3 days at ₹8,000/day = ₹24,000 extra; indirect saved = ₹24,000 → net zero. Duration 15 days, total = 1,96,000 + 1,20,000 = ₹3,16,000 (same cost, shorter time - preferred).
• Step 3: crash C at ₹10,000/day > ₹8,000/day indirect → cost rises. Stop.
• Optimum duration 15 days at ₹3,16,000, against 20 days at ₹3,20,000. (Assumes no other path becomes critical as the path shortens - always re-check the network after each step.)

Where it is used

• Construction and infrastructure: L&T, Tata Projects, NHAI, DMRC and Metro Rail corporations plan with CPM networks, Primavera P6 or MS Project, and monitor against milestone-linked payments.
• IT and consulting: TCS, Infosys, Wipro, Accenture run delivery through PMOs; project/delivery managers report SPI, CPI and burn-down; agile Scrum sprints are the norm for software, with PMP/CSM certification valued.
• Manufacturing and energy: plant commissioning, new line installation, NTPC and refinery turnarounds - shutdown scheduling is pure critical path work.
• Roles for graduates: project coordinator, PMO analyst, business analyst, planning and scheduling engineer, event and new-store rollout managers in retail and QSR chains.

Interview questions

• Q: How does a project differ from routine operations? A: A project is temporary and produces a unique output with a defined end, while operations are ongoing and repetitive.
• Q: What is the critical path and why does it matter? A: It is the longest path through the network with zero float; it determines the minimum project duration, so any delay there delays the whole project.
• Q: Difference between CPM and PERT? A: CPM uses single deterministic durations and focuses on time-cost trade-off; PERT uses three probabilistic estimates to compute expected time and variance, suited to new or research work.
• Q: What is total float, and how is it different from free float? A: Total float is the delay possible without delaying the project; free float is the delay possible without delaying the immediately following activity.
• Q: What is crashing and when do you stop? A: Shortening critical activities by adding resources, cheapest cost slope first; stop when the extra direct cost per day exceeds the indirect cost and penalty saved per day.
• Q: How do you handle scope creep? A: Freeze a baseline scope statement and WBS, route every change through formal change control with cost and schedule impact, and get written sponsor approval.
• Q: A project shows CPI 0.85 and SPI 1.05 - what does it mean? A: It is ahead of schedule but over budget, so cost control, not schedule acceleration, needs attention.

Common mistakes

• Treating the longest *number of activities* as the critical path instead of the longest *duration*.
• Forgetting to re-identify the critical path after each crashing step, so a parallel path silently becomes critical.
• Writing the PERT mean as (a + m + b)/3, or adding standard deviations instead of variances.
• Assuming the project will finish in TE days with certainty - the probability at the expected time is only 50%.
• Confusing a Gantt chart with a network: the bar chart shows timing but not dependencies or float.

Related topics

• Operations management · Total quality management · Supply chain management basics · Procurement and purchasing · Capital budgeting and project appraisal