The practitioner accounts, the official standards and the research on why projects overrun, in one ordered list.
Project management reading splits into three kinds of book, being the practitioner accounts of how the work actually goes, the standards that organisations and certifications are built on, and the research on why projects overrun. This list carries all three. It opens with the books that improve the week you are already in, moves through the guides you need when your organisation runs a formal method, and closes with the classics on people, risk and estimating that explain why the same failures keep turning up decade after decade.
Berkun ran projects on Internet Explorer and Windows, and he writes about the parts a method leaves out, including how to run a meeting that decides something and what to do once the schedule is already lost. Start here if you want one book that changes how you work on Monday.
Flyvbjerg built a database of more than sixteen thousand projects and found the same pattern repeating, which is planning too fast and building too slow. Reference class forecasting is the single most useful technique in this list for anyone who has to commit to a date.
The seventh edition moved from a catalogue of processes to twelve principles and eight performance domains, so it now reads as a way of thinking rather than a checklist. Read it for the shared vocabulary your project office and your auditors already use.
The manual behind PRINCE2, where the business case, product based planning and management by stage boundaries do most of the real work. Essential if you sit in UK public sector or regulated delivery, because the method is assumed rather than chosen.
Produced jointly by PMI and the Agile Alliance, it maps adaptive delivery onto the language a traditional project office already speaks. The suitability filters and tailoring guidance make it the bridging document when you have to explain an iterative approach to a governance board.
DeMarco and Lister argue that the major problems of the work are sociological rather than technical, and they back it with data on interruption, office design and how teams form. It explains why a well planned project still slips when the environment around it is wrong.
Kendrick turns his PERIL database of failed projects into identification checklists you can run against a plan. The scope, schedule and resource categories give a risk workshop the structure it usually lacks.
The source of the observation that adding people to a late project makes it later, and still the sharpest writing on why software schedules behave the way they do. The anniversary edition carries No Silver Bullet, which earns the cover price on its own.
A novel in which a manager is handed far more teams than the work needs and turns the surplus into an experiment about staffing, pressure and estimating. The journal entries at each chapter end carry the argument if you want the short version.
Written for the many people who run projects without the title or the authority, and it spends most of its length on influence rather than on scheduling. Good for product people, marketers and analysts who inherited a project and a deadline together.