mostraligabue
» » Identifying and Managing Project Risk: Essential Tools for Failure-Proofing Your Project

ePub Identifying and Managing Project Risk: Essential Tools for Failure-Proofing Your Project download

by Tom Kendrick PMP

ePub Identifying and Managing Project Risk: Essential Tools for Failure-Proofing Your Project download
Author:
Tom Kendrick PMP
ISBN13:
978-0814413401
ISBN:
0814413404
Language:
Publisher:
AMACOM; 2 edition (February 18, 2009)
Category:
Subcategory:
Management & Leadership
ePub file:
1586 kb
Fb2 file:
1727 kb
Other formats:
azw lrf doc txt
Rating:
4.7
Votes:
384

Projects-especially complex ones-are inherently risky. Between time constraints, technical challenges, and resource issues, things can easily go wrong-making the identification of potential risks an essential component of every project manager's job.

It’s no wonder that project managers are increasingly focusing their attention on risk identification. Identifying and Managing Project Risk is a practical guide to minimizing the possibility of failure in critical projects. The book takes readers step by step through every phase of a project, showing them how to consider the possible risks involved at every point in the process. Relevant figures and diagrams support the text and illustrate key scenarios

Project Risk Management Guidelines: Managing Risk in Large Projects and Complex Procurements

Project Risk Management Guidelines: Managing Risk in Large Projects and Complex Procurements. 61 MB·22,836 Downloads. and product names used in this book are trade names, service marks, trademarks or registered Project Risk. Developing Capacities for Teaching Responsible Science in the MENA Region: Refashioning Scientific Dialogue Identifying and Managing Project Risk: Essential Tools for Failure-Proofing Your Project. 95 MB·178 Downloads·New! a lack of adequate resources.

It stands to reason that project risk management is one of the most important areas making up the Project Management Body of Knowledge (PMBOK)

It stands to reason that project risk management is one of the most important areas making up the Project Management Body of Knowledge (PMBOK). 'Identifying and Managing Project Risk'' is an immensely practical guide that helps readers minimize the possibility of failure in critical projects by identifying every possible risk. and then managing it effectively.

Start by marking Identifying and Managing Project Risk: Essential . Required reading for project management classes. TOM KENDRICK has over 35 years of project and program experience, including senior positions with Hewlett-Packard and Visa.

Start by marking Identifying and Managing Project Risk: Essential Tools for Failure-Proofing Your Project as Want to Read: Want to Read savin. ant to Read. A pretty useful book detailing common risks as well as approaches to risk management. Not sure why one would read it outside of a classroom, though.

Important projects tend to be time constrained, pose huge technical challenges, and suffer from a lack of adequate resources. Identifying and Managing Project Risk, now updated and consistent with the very latest Project Management Body of Knowledge (PMBOK)® Guide, takes readers through every phase of a project, showing them how to consider the possible risks involved at every point in the process.

Books Movies Music Classical All Products Sellers. Identifying and Managing Project Risk: Essential Tools for Failure-Proofing Your Project. Learn how you can guard against failure, eliminate surprises, and keep projects on task. For all enquiries, please contact Herb Tandree Philosophy Books directly-customer service is our primary goal.

Tom Kendrick is an internal project management consultant for Visa In. and the author of Results Without Authority (978-08144-7343-6). He has more than 30 years of project management experience, twelve of which were spent as a part of the Hewlett-Packard Project Management Initiative. I found the book to be very informative. As a seasoned, senior level PM, the terminology and examples used were familiar to me. I don't recommend the book for entry level Project Managers or non management personnel. 2 people found this helpful.

We’re dedicated to reader privacy so we never track you. We never accept ads. But we still need to pay for servers and staff. I know we could charge money, but then we couldn’t achieve our mission: a free online library for everyone.

Therefore, perhaps the most essential component of every project manager?s job is the ability to identify potential risks before they cause unnecessary headaches and turmoil all around. Fully updated and consistent with the Risk Management Professional (RMP) certification and the Guide to the Project Management Body of Knowledge (PMBOK?), Identifying and Managing Project Risk remains the definitive resource for project. managers seeking to be pro-active in their efforts to guard against failure and minimize unwanted surprises

Projects—especially complex ones—are inherently risky. Between time constraints, technical challenges, and resource issues, things can easily go wrong—making the identification of potential risks an essential component of every project manager's job.

Fully updated and consistent with the Risk Management Professional (RMP) certification and theGuide to the Project Management Body of Knowledge (PMBOK®), Identifying and Managing Project Risk remains the definitive resource for project managers seeking to guard against failure.

Drawing on real-world situations and hundreds of examples, the book outlines the risk management process and provides proven methods for project risk planning. Readers will learn how to use high-level risk assessment tools, implement a system for monitoring and controlling projects, and properly document every consideration. Analyzing aspects such as project scope, available resources, and scheduling, the third edition also offers fresh guidance on program risk management, qualitative and quantitative risk analysis, simulation and modeling, and significant "non-project" risks.

This practical book will help readers eliminate surprises and keep projects on track.

  • Short and simple is all that is needed for this reference. This book will help you understand and manage risk simple. We used this as our course book for Risk Analysis with UCLA. This book will provide you with an understand and methods to define, analysis, record and update risks.
    I understand there was a review concerning this book being aimed at the IT industry and although it is used as references, this book and its methods can be used for any industry with success. It provides a clear and simple understanding of how to apply risk methods to manage any kind of risk.
    My risk bible.

  • I found the book to be very informative. As a seasoned, senior level PM, the terminology and examples used were familiar to me. I don't recommend the book for entry level Project Managers or non management personnel.

  • This book makes Risk Management interesting and understandable. If you are trying to get your arms around this subject, I can recommend Tom's book. He explains things in a simple and clear way. I had several epiphanies in the first few chapters alone. I can recommend this book.

  • Very complete, well structured, easy to follow and understand. This is not a simple topic and can be overdone, but in spite of being a bit academic at times, is well covered in this book.

  • This is a wonderful book summarizing the authors lengthy PM experience and collection of over 600 cases of project failures. The Panama Canal projects provide historically interesting case of poor and eventually much-improved project decisions and management. Kendrick shares his enthusiasm for the PM discipline. The emphasis is on moderate-sized technical projects.

  • Great book.

  • Some old school useful points, but ad-hoc and mis-targeted (as one other reviewer notes ... who is to read this? ... overload of heuristic lists for beginners, but experienced managers already know it).

    Kendrick uses throughout the example of the Panama Canal project, both the original French commercial failure, and the later U.S. Government success. But most of the key lessons from both could only be implemented by the project "sponsor" (Kendrick's term) not the PM, yet Kendrick writes a book for PMs. E.g. Roosevelt intervened to eliminate the 7-person council that couldn't decide anything. And there must be a lesson in here about government vs. private projects that Kendrick overlooks.

    Kendrick assumes infinite persuasiveness on the part of PMs, both to persuade their bosses/sponsors and their workers to follow ad-hoc guidelines that are never quantitative. For example, he advocates traditional reserves. Most projects in modern organizations aren't allowed to manage reserves anymore, these have been scooped up by higher levels.

    Other than keep track of thousands of list items and "persuade" others to pay attention to them, there are no concrete suggestions on what to do to get others motivated and manipulate the outcome. Kendrick winds up recommending that you draw a line and just cancel projects that go over it. He justifies this with a very clever but off-target bidding exercise in which students bid on a dollar bill, with the stipulation that the 2nd highest bidder also has to pay, and bidding typically runs over $2.

    For a more concrete and certainly more concise approach, see Economic Optimization of Innovation & Risk, which gives a quantitative model of the economic factors affecting both project outcome and reliability of the delivered system (crash rate), and works a difficult example of how to fix a project that is not meeting its goals.

    Kendrick's book is not without use or some interesting points. There are lots of quotes throughout that almost by themselves make the book worth reading, like Roosevelt "Far better it is to dare mighty things..." and Patton "A good plan violently executed right now is better than a perfect plan executed next week." Although Kendrick's 360 pages of lists seem to be guiding us toward next week or later. The book depends heavily on external databases, PMBOK and PERIL, with selections from the later included, which again are just anecdotal heuristics. Don't get me wrong, I use heuristics myself, but one needs a short list of them, and a quantitative model to justify them.

    Kendrick covers some of the problems of project sponsors attempting too much. But is clueless as to how to fix it. And if anyone has worked for Elon Musk or Jeff Bezos, one knows that one doesn't just schedule a couple hours of their time to go over detailed lists. The "modern" boss simply isn't available to hear that something isn't going to work, and will just replace a PM who doesn't go along. The book needs to be re-targeted.

    Some of the things Kendrick proposes, such as lean, quick projects, can backfire and increase risk. Again the quantitative model is lacking. A few figures are unreadable in the eBook version, and all have very small print.

  • Its a textbook. Referenced it a lot for class, but didn't exactly use it for light enjoyable reading.