I'm the author and wanted to make sure you were informed there is a new, updated edition of this book, and its now called Making Things Happen: Mastering Project Management. It has been revised, polished, and enhanced, with 120+ new exercises, a discussion guide, improved footnotes, and much more.

Since the old edition listed on this page is out of print and hard to find, it's selling for twice the list price of the new edition, and, if you care, I get no royalties from used book purchases. If you really really want it for some reason, go for it, but I wanted to make sure you knew there's a better, and likely cheaper edition available.

Cheers and happy reading.

I'm a rookie, so a playbook that organizes my thinking and allows me to execute the plays each day is perfect for what I need. I was surprised at how much of the role of project manager I do right now, and how much of the work is accessible if not desirable to me. The general feeling upon conclusion of the book is that I was just short of an epiphany in thinking, but it helped solidify my suspicions about project management:
-it is about getting things done through others;
-it requires a disciplined mind and organizational ability;
-it can be learned;
-it can be more rewarding than being an individual contributor.

Mr. Berkun has a lot of commercial software development background, so you'll need to map his model onto yours, but this isn't difficult. The processes for new projects are identical to maintenance work, only you have a smaller timeline and a more focused objective. Really, the ideas and practices scale very well.

Where I was put off, somewhat was in how the footnotes were organized, and how his anecdotes tended to end. Footnotes go at the bottom of the page or, much less ideally, at the end of the chapter. Putting them at the back of the book is the least helpful of the options. I'd have rather seen long parenthetical ramblings than a collection of now-contextless footnotes to read.

The anecdotes were illustrative, but lacked some kind of conclusion or resolution almost every time. "We had a problem, I discovered 'x', and we applied it." So how did it turn out? There's no reflection upon the efficacy of his examples in many cases, and it's an annoying method of storytelling.

Overall, I'm pleased that I found the book, and plan to use it in my expanded role at work. Once I develop some mastery of daily/ weekly/ monthly planning and execution, I'm sure I'll be able to move onto more advanced study, but I'm not ready, and this book is clearly for rookies with some self-awareness.

-C