43 Folders

Back to Work

Merlin’s weekly podcast with Dan Benjamin. We talk about creativity, independence, and making things you love.

Join us via RSS, iTunes, or at 5by5.tv.

”What’s 43 Folders?”
43Folders.com is Merlin Mann’s website about finding the time and attention to do your best creative work.

Review: Scott Berkun's 'The Art of Project Management'

oreilly.com — Online Catalog: The Art of Project Management

O’Reilly recently sent me a review copy of Scott Berkun’s The Art of Project Management. I’ve read a couple chapters through, and—as the author himself has recommended—have grazed through a bunch of the sections that looked especially interesting to me. See, I have a marker for a non-fiction book that’s really connecting with me—as I’m reading it, I find myself repeatedly cursing the fact that it didn’t exist earlier. I’m definitely feeling that with this one.

Where so many Project Management books fetishize GANTT charts, waterfalls, and abstract planning methods, most of Berkun’s book lives much further down in the trenches—where misunderstandings happen, dates slip, and bad decisions threaten to derail your project. The book is full of really practical advice on handling these challenges in the real world. And, yes, I really wish it had existed 7 or 8 years ago. As it is, many of my bouncer skills were primitively self-taught.

One of my favorite chapters, as you might guess, is called “How Not to Annoy People: Process, Email, and Meetings.” It includes a useful bit on how to write good email that I wish everyone who owned a computer would consider reading and then stapling to their monitor.

Offer an action and a deadline. The best kind of email has a specific intention or request that is clearly stated, and, if appropriate, is tied to a reasonable deadline. It should be easy for people reading the email to understand why they are receiving it, how they are impacted by the action, and what they need to do (before the deadline). Assuming you enforce the deadline (“Requests must be in to me by Friday”), you set yourself up for people to be attentive to future actions you communicate through email, which puts you in a position of power.

There’s a PDF of a sample chapter (Chapter 3: How to figure out what to do) on the O’Reilly book site to give you a flavor. But if your job includes any kind of project management especially in the world of web development, you might want to have a look at this. The skills Berkun encourages go beyond one team member’s role, though—communicating well, meeting deadlines, and moving your piece of the project forward are the skills that make anyone the team’s MVP.

Merlin's picture

I know what you mean,...

I know what you mean, Todd. Worse still is how full of jargon many are. My problem wasn’t so much in using tools as in knowing how to manage expectations and communicate efficiently with very different personalities. That’s the hard stuff.

Dynamics of Software Development and Rapid Development are two I learned a lot from (make that three I love from MS people).

As far as other, non-software books, the pickins is thin, in my experience. I’ve bought probably half a dozen okay-quality books just so I’d be up to date on lingo, but I haven’t been really bowled over by a PM book in a while.

Let me pick through some boxes and see if any jog my memory.

 
EXPLORE 43Folders THE GOOD STUFF

Popular
Today

Popular
Classics

An Oblique Strategy:
Honor thy error as a hidden intention


STAY IN THE LOOP:

Subscribe with Google Reader

Subscribe on Netvibes

Add to Technorati Favorites

Subscribe on Pageflakes

Add RSS feed

The Podcast Feed

Cranking

Merlin used to crank. He’s not cranking any more.

This is an essay about family, priorities, and Shakey’s Pizza, and it’s probably the best thing he’s written. »

Scared Shitless

Merlin’s scared. You’re scared. Everybody is scared.

This is the video of Merlin’s keynote at Webstock 2011. The one where he cried. You should watch it. »