Introduction to Project Management
This page provides an easy-to-understand guide on successful management of projects.
What project management actually is, what a project manager does all day, how to tell a project from routine work, and why the discipline exists at all.
The project lifecycle in four phases — initiation, planning, execution, closing. What each one decides, what it leaves behind, and what breaks when one is skipped.
The four things every project plan has to settle — what you are delivering, by when, with whom, and what could go wrong — and what goes wrong on real projects when any one of them is left vague.
Why most project failures are coordination failures, the three things that need managing — team, stakeholders, communication — and the symptoms when each is thin.
The three ways to look at the same project work — by date, by state, by priority. Which question each one answers, who should live in which, and how to pick.
Tracking project progress as a loop — measure, compare, decide, tell — the symptoms when each step is thin, and why accurate status can still hide a missed date.
Why the last two days of a project decide what the organisation keeps, the symptoms of thin closure months later, and how much closure a project of each size needs.
The five variables that separate projects that work from projects that fail, how case studies mislead through hindsight and survivorship bias, and how to read one usefully.
Short answers to the questions project managers actually ask — scope growth, the 90% problem, estimates, tool adoption, Agile, slipping dates — each linked to the full chapter.
What actually turns project management knowledge into skill: honest feedback loops, credentials that make your work legible to strangers, and the directions the role widens in.