The book's examples relate to software projects but could easily be transposed into any team effort. Any time you have to work with more than 2 people someone needs to lead the effort. If you don't know who that is, it might be you. It's easy to visualize how these guidelines can be applied to projects like moving your office location or even (and I have suggested this to at least one person) planning your wedding. If you need to herd the cats, here are tools to do it.
This is not hard-core project management. This is enough to get the neophyte who was drafted up to speed. Bob's writing style is conversational and breezy enough so that this isn't a slog.
A slim volume of practical insights you can immediately put into practice in your business, personal projects, or non-profit and volunteer pursuits. Whether you are leading a committee and whether it is a short-term or long-term project, the tips on how to initially organize and then keep an initiative moving forward rather than stalling out and treading water (or worse yet, never finishing ... the never-ending project ...), this is a worthwhile reference to keep on your business bookshelf and share with others.
I think it is a pretty good manual for those who are not exposed to Project Management. Can be used as a guide for a small project. Actually almost every statement is very valuable and an extract of project methodology(ies) for everyone who "has been volunteered". I really appreciate the effort of Bob Lewis.
I thought it was a pretty good book even though I gave it two stars.
When you read PMBoK, you always try to apply it to the projects you are working on and if they are small you can't keep but wondering whether all this grand project management actually applies to your 20K 3-month project.
So it's really important to separate bare minimum from everything, because in reality what happens is that many people say: oh, PMBoK is for big projects, we are not going to do any of it. So you rush into a project with no owner, couple of requirements and zero completion criteria and couple months later can't help but wondering whether your project is complete.
This book describes bare minimum that needs to be completed on any project in order for it to be successful.
Pretty good. Pretty brief. Readable in an hour or so, taking notes. Most of this stuff is meant for IT project management, but could be applicable to any sort of project in general. The simple things are hard. Get an "executive sponsor" to take responsibility for the project, get a "work break-down structure" AKA "outline" in place, don't improvise, and know when it comes to an end. I can only give it a four, because things are so shit at my job, I doubt we could even do a quarter of the very simple things asked for in implementing this.
Since I want to do PM for myself, I am guessing the outlining and timelining are probably key for me.
Bob Lewis cuts through the theoretical techniques for project management and provides advice and techniques that can be put into practice in the real world. Great read and worthy to reread periodically.