Personal MBA, Book 1
The reading time for the first book the Personal MBA is almost up. I’ve read most of it, and should be able to complete it before the time is up.
The Art of Project Management is a good book. It reads easily and covers its material well. It covers what I would consider to be all the topics, including the human ones. The coverage of the “human” factors is why I would consider this book a must read for any aspiring project manager, or a current manager who feels disconnected with his team.
The book avoids advocating any specific methodology. The author goes out of his way to leave many things ambiguous, such as the amount of scheduling and what should be on the schedule. His advice is “check with the people on the project, and let them decide, or at least advocate, how much process there should be.”
The book does state that there are certain stages of any project that do require managing: Requirements, Design, and Implementation, in this order. These phases are divided up by their deliverables, the Marketing Requirements Document, the Vision Document, and the Schedule. One perusing the book might think the author advocates a waterfall method, but he doesn’t. These documents are “living” and are meant to coexist and be kept up in tandem.
Where the book really is useful is in the chapters such as “Where Ideas Come From”, “Communications and Relationships”, and “Why Leadership is Based on Trust”. No chapter is “revolutionary”, but all of them do provide common sense and good points to remember when going through the various phases. He provides lots of lists and bullet points for things such as gathering and refining ideas and communicating with team members. He even offers advice on connecting with the team and establishing trust, something that most project management books don’t offer.
Lastly, I enjoyed the notes to the chapters. In looking through these, I’ve expanded my reading list quite a bit and plan on reading many of his recommendations.
Overall, I would recommend the book along with a book on a specific methodology applicable to your field. In my field, software, I would recommend an agile methodology, perhaps Scrum.