PERT provides a sophisticated framework for managing temporal uncertainties in large-scale projects. Evaluate the strategic utility and inherent limitations of this technique in complex environments.
15 marks · directive: Evaluate
The core of a good answer
PERT models a project as a network of activities, uses three time estimates to compute an expected time and its variability, identifies the critical path and estimates the probability of meeting a deadline, which makes it strategically useful for planning and control of large one-off projects; but subjective estimates, the assumption of a fixed network, unwieldy charts and the absence of cost estimates limit it in complex, changing environments.
An outline written by upsc.help, not an official UPSC answer; every fact checked by a separate review. How we work
What the question asks
Evaluate means judge worth. The marks (5+5+5) suggest: explain the technique, assess its strategic utility, and assess its limitations, with a conclusion on its use in public projects.
Answer outline
Introduction
Programme Evaluation and Review Technique (PERT) was developed in 1958 for the US Navy's Polaris missile project by the Navy Special Projects Office with Lockheed Aircraft and Booz Allen Hamilton (Charles E. Clark is credited with its development). The Critical Path Method was developed by DuPont around the same time.
The technique
- Break the project into activities and events; draw the network showing dependencies.
- Three estimates per activity: optimistic (o), most likely (m), pessimistic (p).
- Expected time te = (o + 4m + p) / 6; standard deviation = (p − o) / 6.
- Illustration: o = 4, m = 6, p = 14 days gives te = 7 days and standard deviation about 1.67 days.
- The longest path is the critical path; slack shows flexibility on other paths.
Strategic utility
- Makes dependencies and the critical path explicit, so management attention goes where delay matters.
- Estimates the probability of completion by a given date, useful for commitments and risk management.
- Helps coordinate many agencies and contractors in large infrastructure, defence and space projects.
- Supports management by exception and progress reviews.
Inherent limitations
- Time estimates are subjective and prone to error, especially for novel tasks.
- Assumes a known, fixed network; complex projects change scope during execution.
- Network charts become large and unwieldy, and PERT is not easy to scale down for smaller projects; it typically uses no cost estimates for activities.
- Unexpected events can make predictions inaccurate.
Conclusion
PERT remains a valuable discipline for planning under uncertainty, but in complex environments it should be combined with cost and resource scheduling, risk analysis and frequent updating.
Examples and data to cite
- Polaris missile project (1958) as the origin of PERT.
- CPM, developed by DuPont at about the same time, uses one time estimate per activity, while PERT uses three.
Facts to remember
- PERT expected time: te = (o + 4m + p) / 6.
- PERT standard deviation of an activity: (p − o) / 6.
- Critical path: the longest path through the network, with zero slack.