Berlin Brandenburg Airport began construction in 2006 and was first due to open in October 2011. It opened on 31 October 2020. The main single cause was a fire-protection and alarm system that failed its mandatory acceptance test and had to be largely rebuilt, on top of a general planner's insolvency, dismissed architects and widespread wiring problems. Its budget stood at €2.83 billion by 2009; one 2018 forecast reached €10.3 billion.
Now look at the other end. The Empire State Building went from the start of construction on 17 March 1930 to its opening on 1 May 1931, about thirteen and a half months. The Guggenheim Museum Bilbao opened on 18 October 1997 and is reported to have been built on time and on budget, which, as its own encyclopaedia entry says, is rare for a building of its kind. Same human species, same arithmetic. What differed was how the work was defined, planned, led and checked, which is what project management studies. This piece is the foundation: what a project is, how to choose a way of working, and why plans are so often too optimistic.
- Who takes it
- Part 1 of the Project Management minor, a short route that sits beside many majors: it is not a degree of its own but adds a skill to degrees such as Civil Engineering, Computer Science, Architecture or Business Administration. Universities teach it as an engineering-management or business elective, often in the final years alongside a capstone. Professional bodies (PMI, PeopleCert for PRINCE2, APM, IPMA) teach and certify it too.
- What it is for
- Getting a one-off piece of work finished, with agreed results, by people who are not otherwise working together.
- Comes after
- Nothing is required. Easier first reads: Operations Management (34/52), for routine work, and Judging a Proposal: The Outside View (04/10).
- Leads to
- Scope, Estimation & Scheduling (36/91), Agile, Scrum & Kanban (36/92), Leading Projects (36/94) and, through 36/91, Risk, Cost & Project Control (36/93).
- What this piece gives you
- You will not hold a certificate after this. You will be able to say whether something is really a project, pick a sensible life cycle, read the main standards, write a one-page charter and mistrust your own first estimate. Neighbours: Construction Management (34/70), which tells the megaproject story in detail, and Organizational Behavior & Leadership (34/53).
A project is temporary, unique and aimed at a result
PMI's standards define a project as a temporary endeavour undertaken to create a unique product, service or result. Three words do the work. Temporary: it has a beginning and an end, and it ends when its goal is met or abandoned. Unique: even if it resembles earlier work, something differs, whether the site, the team or the technology. Result: someone wants a defined outcome, not just activity. Operations are the opposite: ongoing, repeating, run to a steady cycle. A payroll run each month is operations; replacing the payroll system is a project, and the runs afterwards are operations again.
The border is not always clean. A town's annual street fair has a date and an end, so each edition can be called a project, yet its playbook is routine. Good managers do not argue about the word; they ask whether the project tools (a defined end, a charter, a risk list) would help or just add paperwork.
Eight pieces of work. Choose Project, Operations or Both, and read why.
Without JavaScript: building a school wing, moving offices, replacing payroll software and writing a thesis are projects; running a timetable, processing a monthly payroll and answering support tickets are operations; an annual fair with a fixed playbook is both.
The triple constraint, and what it leaves out
A classic picture ties every project to three corners: scope (what is built), time and cost. Change one and another moves. The triangle goes back to Martin Barnes, who drew a cost, time and quality version in 1969, and the folk slogan is "good, fast, cheap: pick two". It is a useful warning against promising everything. Its critics make a fair point too: a project can hit all three and still fail. Roger Atkinson argued in 1999 that cost, time and quality are "two best guesses and a phenomenon" and that success also depends on benefits to users and the organisation, and on stakeholders' satisfaction.
The modern way of saying this is three layers of success. The output is what you deliver (a new booking system). The outcome is the change it causes (customers finish bookings in half the time). The benefit is the value the organisation gets (more bookings, lower support cost). A project can deliver the output on time and on budget while the benefit never arrives. A good charter names all three, and says how each will be checked.
Life cycles: predictive, iterative, incremental, adaptive and hybrid
A life cycle is the pattern in which a project moves from start to finish. In the vocabulary used by PMI, predictive (plan-driven, "waterfall") fixes scope early, plans the whole and delivers at the end. Iterative cycles refine a product through repeated rounds of building and feedback. Incremental delivers working pieces one at a time. Adaptive (agile) combines both in short cycles, with scope that is expected to change. Hybrid mixes approaches, for example a predictive frame around a software component.
Nobody wins this argument in general, and sneering at either side misses why each exists. Construction, aerospace and pharmaceutical work use predictive methods for good reasons: concrete cannot be re-poured weekly, a regulator wants a documented design, and a change late is very expensive. Software teams often use adaptive methods because the cost of changing code is low and the real requirements only appear when users touch something. Two questions do most of the choosing: how sure are we of what is wanted, and how sure are we that we can build it? The third is how costly it is to change late.
A rule of thumb in the spirit of the Stacey matrix, not a standard: add the first two scores (0 to 20); 0 to 5 suits predictive, 6 to 9 incremental, 10 to 13 iterative, 14 or more adaptive; if the cost of late change is 8 or more and the total is 10 or more, hybrid.
Without JavaScript: a bridge with a known design (both uncertainties low) is predictive; a new app for an unknown audience (both high) is adaptive; a hospital with a changing clinical model inside a fixed building is hybrid.
The bodies of knowledge: several books that disagree politely
Project management is documented in standards, each issued by a body with its own emphasis. The table gives the current editions as published; check the issuer before you buy anything, since editions change.
| Standard | Issuer | Edition and note |
|---|---|---|
| PMBOK Guide | PMI (US, founded 1969) | First edition 1996. The 7th (2021) replaced the ten knowledge areas with 12 principles and eight performance domains. The 8th (published November 2025) has six principles and seven performance domains. |
| PRINCE2 | PeopleCert (UK origin; formerly AXELOS and the UK government) | 7th edition, 2023: seven principles, seven practices (formerly "themes") and seven processes. |
| APM Body of Knowledge | Association for Project Management (UK, Royal Charter 2017) | Now in its 8th edition. |
| ICB4 | IPMA (International Project Management Association, Europe-rooted) | Describes the competence of a person (People, Practice, Perspective), not only a process. |
| ISO 21502 | ISO | 2020, guidance on project management. Its sibling ISO 21500 was reissued in 2021 as Project, programme and portfolio management: context and concepts. Guidance, not a certifiable standard. |
They share more than they differ: a business reason, defined roles, planning in stages, control of change, learning at the end. They differ in tone. PRINCE2 is a method, with named processes and controlled stages. The PMBOK Guide is a body of knowledge that has moved from processes toward principles and tailoring. IPMA's ICB asks who you must be to run a project. Certification follows: PMI awards the PMP (its first exam was in 1984) and the CAPM; PeopleCert awards PRINCE2 qualifications; IPMA and APM have their own levels. Whether a certificate helps a career varies by country and industry, so treat salary claims from sellers of courses with caution.
Why projects fail: the inside view and the outside view
Psychologists Daniel Kahneman and Amos Tversky named the planning fallacy in 1979: people predict by imagining how this project will go, and forget how projects like it went. In a 1994 study, 37 psychology students estimated when they would finish their senior theses: their average guess was 33.9 days, their average worst case 48.6 days, and the actual average 55.5 days, with only about 30% finishing when they had predicted. Even the worst case was too kind.
Bent Flyvbjerg, who has built a very large database of project outcomes, adds a second cause: strategic misrepresentation, when the projects that win approval are those that look cheapest, so honest estimates lose to optimistic ones. In How Big Things Get Done (2023, with Dan Gardner) he reports on a database of about 16,000 projects across more than 20 fields and 136 countries. As published, only 8.5% were on budget and on time, and only 0.5% were on budget, on time and delivered the promised benefits. IT projects add a fat tail: Flyvbjerg and colleagues' 2022 study of 5,392 IT projects concludes that their cost risk is far larger than usually assumed, with a few overrunning by multiples. (The Standish Group's widely quoted CHAOS success rates are criticised: Eveleens and Verhoef, IEEE Software, 2010, showed they treat any deviation from an original estimate as failure. This piece uses none of them.)
The remedy he and the UK Department for Transport promote is reference-class forecasting: place your project in a class of similar ones and use the spread of what happened to them. His other rule, "think slow, act fast", means spending effort before committing, when changes are cheap, then delivering quickly. Not everyone agrees on how general the numbers are, but the habit of comparing a plan with a distribution is hard to argue with. Try it with your own estimate.
The reference classes here are invented for illustration, shaped like the published pattern (most outcomes near the estimate, a long tail on the high side). They are not data from any study; your own organisation's history is the better source.
Without JavaScript: in the invented "custom software" class, the median overrun is 15% and one in ten ends 120% or more over, so a 10% headroom covers only about 42% of the outcomes.
Template: a one-page project charter
The charter (PMI's term; PRINCE2 has a project brief) is the document that authorises the project and says what it is for. It is short on purpose. If the sponsor, the team and the people affected cannot agree on one page what done means, the later pages will not rescue it. Fill in the form, then copy it as text. Nothing is stored: when you close the page, it is gone.
Without JavaScript: write down the name, sponsor, problem, output, outcome, benefit, three measurable success criteria, what is in and out of scope, key dates, budget, top risks, assumptions and who decides what.
What a graduate just sees
- A project is temporary, unique and aimed at a result; routine work is operations, and each needs different tools.
- On time and on budget are not the same as successful: output, outcome and benefit are three layers.
- Life-cycle choice follows uncertainty about what is wanted, uncertainty about how to build it and the cost of changing late, not fashion.
- The standards (PMBOK, PRINCE2, APM, ICB4, ISO 21502) share a core and differ in tone; know which one your client or employer uses.
- Your own estimate is the inside view and is usually too kind; ask how similar projects ended.
- Big overruns come from optimism and from selection by cheapness, and IT cost risk has a fat tail.
- A charter that one page cannot hold is a project nobody has agreed on.
Where it shows up next
- Scope, Estimation & Scheduling (36/91): breaking the work down and finding the critical path, the first things a charter turns into.
- Agile, Scrum & Kanban (36/92): the adaptive family in detail, and where it does not fit.
- Risk, Cost & Project Control (36/93): contingency, earned value and the pre-mortem.
- Leading Projects (36/94): stakeholders, teams and closing.
- In the world: a bridge, a hospital wing, a product launch, an election-system upgrade, a thesis or a wedding.
If you want to go deeper
- 📘 Textbooks. Bent Flyvbjerg and Dan Gardner, How Big Things Get Done (Currency, 2023), the evidence on why big projects fail and what works; and the PMBOK Guide (PMI, 8th edition, 2025) with PMI's Standard for Project Management, the reference most courses follow.
- 📘 Gentler. Frederick Brooks, The Mythical Man-Month (1975; anniversary edition 1995), essays on running a large software project that still read freshly.
- 🌐 Free course. MIT OpenCourseWare 1.040, Project Management (Spring 2009), with lecture notes, aimed at infrastructure projects.
A project is a temporary effort to create something unique, and it succeeds only if the benefit arrives, not just the deliverable. Match the way of working to your uncertainty, learn the vocabulary of the main standards, and treat your own estimate as one voice against the record of similar projects.
Try this: take a task you have planned lately and write down your estimate. Then find three similar tasks you finished and what they really took. Is your estimate closer to their best case or their typical case?
Sources. PMI, PMBOK Guide editions (1996 to 2025) and PMI's definition of a project; PeopleCert, PRINCE2 7th edition (2023); Association for Project Management, Body of Knowledge; IPMA, Individual Competence Baseline (ICB4); ISO 21502:2020 and ISO 21500:2021; Barnes (1969) on the cost, time and quality triangle; Atkinson, "Project management: cost, time and quality, two best guesses and a phenomenon, its time to accept other success criteria," International Journal of Project Management 1999; Kahneman and Tversky, "Intuitive prediction: biases and corrective procedures" (1979); Buehler, Griffin and Ross, Journal of Personality and Social Psychology 1994; Flyvbjerg and Gardner, How Big Things Get Done (2023); Eveleens and Verhoef, "The Rise and Fall of the Chaos Report Figures," IEEE Software 2010; building dates from the entries for the Empire State Building, Berlin Brandenburg Airport and the Guggenheim Museum Bilbao. The reference classes in the interactive are invented. Go deeper. Meredith, Mantel and Shafer, Project Management: A Strategic Managerial Approach.
- 📘 Flyvbjerg and Gardner, How Big Things Get Done
- 📘 Brooks, The Mythical Man-Month
- 🌐 MIT OCW 1.040