Best Practices for Managing Successful Projects
October 31st, 2006 by HalAwhile back I got a book in the mail with a polite request to review it. This happens about once a month. While I was curious about the title, Rainbows & Ratholes, I kept shuttling the book from bedside table to briefcase to the corner of my desk and back to my briefcase. As luck would have it, a 3-hour flight-delay coincided with the book being in my briefcase. I finished the book. Dan M. Kothari wrote the book as he says, "…to bridge the gap between theory and practice." It seems to be a common theme.
There is much to like in the book, starting with the introduction.
"Successful organizations embrace a projectized culture that is founded on the principles of customer focus, committed sponsorship, trusting relationships, outstanding teamwork, and continuous improvement."
Kothari offers good advice and distinctive perspectives throughout his book
I was struck that Kothari didn't speak about WBS, ROI, CPM, and risk management. But I didn't have to read far before that stood out in his writing. Kothari bounces back and forth from writing an introductory book explaining WBS, etc. to offering real insights on the five issues raised in his Introduction.
I really like the structure of the book. Chapters are short. Chapter titles are accompanied by illuminating subtitles. Each chapter starts with a quote and finishes with a Chapter Summary. Each summary concludes with Learning Lessons to Avoid the Ratholes and Best Practices for Catching the Pot of Gold. Readers will get comfortable with this style.
Kothari offers good advice and distinctive perspectives throughout his book. For instance, in Chapter 7 he writes,
"Preparation of the roadmap is a team effort…(The project manager) gets the team involved during planning."
In Chapter 8 he adds,
"The schedule is not the plan. The schedule is simply one component of the Project Implementation Plan…The plan is revised and fine-tuned as we gain more understanding of the project and its details."
These are the insights that make this book worth reading.
"The sole purpose of a project is to satisfy the client's business and organizational goals and needs."
Chapter 10: "Uncertainty — the only uncertainty" is a great title. His summary point, "When it comes to risk, the project manager thinks like a pessimist and acts like an optimist" falls short of being actionable. If only Kothari had offered some way to encourage project managers to embrace the uncertainty of their situation. I was disappointed.
Still, Rainbows & Ratholes offers a useful perspective for the discerning reader. Take your time with the book. It will payoff for you.
In finishing, Kothari claims, "The sole purpose of a project is to satisfy the client's business and organizational goals and needs." As my UK friends would say, "Full stop."
Related Posts
- Not Managing Perceptions: The 10th Waste of Project Management "Project Quality Management must address the management of the project and the product of the project" (p.180, PMBOK,...
- Managing For A Higher Purpose I found a short article today that supports the point I made in my Project e-Tip this week Keep the Project Mission Aliv...
- Managing Product Development I added a new weblog to my blogroll today. So, what's the big deal? The weblog is by Johanna Rothman. It's titled Man...
- What Are Your New Year’s Lean Resolutions Ralph Bernstein writing at Lean Insider for Productivity Press posted his proposal for 10 Lean Resolutions for the New...
- Project Management Just Unnecessary Overhead? Why fight a company culture that doesn't support project management practices. Instead, go stealth. That's the advice ...











November 1st, 2006 at 9:22 am
Great entry, and great blog! I’m the Editor-in-Chief of RogueProjectLeader.com, and wish I’d come across your site sooner (RPL is currently on a hiatus, but you might find some interesting things in our archive).
Will have to check out Rainbows & Ratholes - thanks for the intro!
November 1st, 2006 at 5:10 pm
Hal,
Thanks for the recommendation. This sounds much like the IMP/IMS (Integrated Master Plan / Integrated Master Schedule) approach where the “Plan” represents the increasing maturity of the project in terms of the customers expectations. The “roadmap” is the path through the Significant Accomplishments that deliver inceasing value (maturity) from the efforts of the project team. Accomplishment Criteria are the “exit criteria” for the tasks that deliver the work in fulfillment of the Signifiant Accomplishments.
The IMP/IMS approach has many other attributes inappropriate for IT or non-defense projects, but the principles of defining the customer’s criteria for assesing value delivery, measuring that value in units useful to the customer and having an Integrated Product Team (IPT) - meaning everyone is on the team and has skin in the game - is the basis of many succesful defense contracts - including a few I’ve planned and particapated in