Identifying And Managing Project Risk: Essential Tools For Failure-Proofing Your Project By Tom Kendrick PMP

Identifying and Managing Project Risk: Essential Tools for Failure-Proofing Your Project By Tom Kendrick PMP List Price: $32.95 Price: $21.75 & eligible for FREE Super Saver Shipping on orders over $25. Details Availability: Usually ships in 2 to 3 weeks Ships from and sold by Amazon.com 48 new or used available from $14.81 Average customer review:

Product Details

• Amazon Sales Rank: #50170 in Books
• Published on: 2009-02-18
• Original language: English
• Number of items: 1
• Dimensions: 1.30" h x 6.36" w x 9.22" l, 1.49 pounds
• Binding: Hardcover
• 368 pages

Features

• ISBN13: 9780814413401
• Condition: New
• Notes: BRAND NEW FROM PUBLISHER! BUY WITH CONFIDENCE, Over one million books sold! 98% Positive feedback. Compare our books, prices and service to the competition. 100% Satisfaction Guaranteed

Customer Reviews

Required reading for all project managers and sponsors
This volume may be the best one I have ever read on the subject of risk in the project arena. Kendrick has captured the best of current practical thinking on project risk and how to identify and manage it. And the author has carefully linked theory and practice to the Project Management Institute's "Project Mangement Body of Knowledge." In addition this book is exceedingly well written and very readable (a rarity in this genre).

Kendrick approaches risk identification from the perspective of the project manager in the areas of scope (project deliverables and product), resources (people, materials, and money), and schedule (time). He addresses each area in a separate chapter with practical advice on how to identify and document potential risks. An aspect of these three chapters I particularly appreciate is the depth of information that allows the reader to address each area of risk at different levels. Kendrick does this by providing an array of analytical tools. For example in Chapter 4, "Identifying Project Schedule Risks," the reader could use the list of common schedule risks and probably account for 80% of the schedule risks for their project, or move to a deeper analysis of risks associated with delays, dependencies, and errors in estimation. In the area of estimation the reader is presented with an array of estimating techniques that can be used as appropriate to detect potential risks in estimation.

Chapter seven on "Quantifying and Analyzing Activity Risk" appears just in time. After reading the first six chapters the reader may throw up their hands and declare "I can't manage all of this!" As an experienced project manager, Kendrick gives us tools to help select the risks to manage. All potential risks on a project are not manageable or worth the time and effort to manage. This chapter gives sage advice on how to select the vital few.

A key element in Kendrick's approach is distinguishing what he calls "activity risk" from "project risk." It is easy for the project manager to focus on risks associated with various activities and forget the larger picture. In fact there may be times when the risks associated with each activity seem minor but when the project is viewed as a whole the project is very risky. Kendrick provides tools for quantifying and analyzing risk at the project level as well as a chapter on managing project level risk.

I end this review with three overall comments. First, pages 17-24 should be required reading for all senior managers and anyone who sponsors a project and there should be a test at the end. The biggest risk for too many projects is unknowing, unthinking, or uncaring managers who are driven by near term profits and stock prices. Second, readers should not be put off by Kendrick's inclusion of statistical and mathematical information. Such information comprises less than 5% of this book and it would be a shame to miss the other 95% due to a fear and loathing of numbers. Finally, if you can't find any other reason to read this gem, read it for the intriguing history of the building of the Panama Canal. If Kendrick ever decides to stop managing projects, he has a bright future as a writer of interesting history.

Practical Risk Management
Reviewed by Al DeLucia
Director
Project Management Division
GSA, Philadelphia

Anyone who - like me -- has struggled to relate the abstract discussion of Risk Management in the PMBOK to actual project management practice will welcome this down-to-earth presentation. This book shows how to incorporate risk management into the planning of your project along the way - the entire way -- of the project development sequence.

Mr. Kendrick had many years of practical project management experience with Hewlett- Packard and headed their in-house project management training and consulting program. Over a period of 10 years, he trained hundreds of project managers at HP, in other organizations world-wide, and at the University of California at Berkeley and systematically collected information about the most significant risks they had encountered in their projects. The result is a database called PERIL (Project Experience Risk Information Library), that contains 222 projects sorted into risk categories based on type and impact. In this book, these results are integrated with the PMBOK processes of project development in a way that shows what project management is really all about.

Anecdotes from the construction of the Panama Canal are interestingly presented at the ends of the chapters. These describe how the concepts of each chapter were applied - or not - first by the French in their failed attempt to build the canal, and then by the Americans in their successful endeavor under the sponsorship of Teddy Roosevelt.

In search of good books on managing project risks
This book provides an overview on how to manage certain types of project risks (some risks are not covered, e.g. financial) and, implicitly, only IT projects and not other types of projects (e.g. construction). Like many books on this topic, the treatment is uneven. The strengths are its logical structure and clear exposition. I knocked off 2 stars because a) there is a disconnect between the text (mostly IT-related) and case study (building of Panama Canal), and b) neglect of contractual issues, the key instrument of risk management. This is the book for you to read if you have no idea about project risk management.