RISK MANAGEMENT a Guide to Managing Project Risks and Opportunities

Total Page:16

File Type:pdf, Size:1020Kb

RISK MANAGEMENT a Guide to Managing Project Risks and Opportunities Project and Program hbNIVEE31DAD 3E BELGhtAF4G Gsiito de Esrlidicls de Posyrado y Edt~cactoriZontmua RISK MANAGEMENT A Guide to Managing Project Risks and Opportunities Edited By: R. Max Wideman Fellow, PMI A Publication of the Project Management Institute Four Campus Boulevard Newtown Square, Pennsylvania 19073 USA 610/356-4600 Fax: 610/356-4647 E-mail: [email protected] Web: http:/,www.pmi.org Library of Congress Cataloging-in-Publication Data Foreword Edited by: Wideman, R. Max. Project and program risk management: a guide to managing project risks This publication is the second in a series of nine handbooks devel- and opportunities/R. Max Wideman oped by the Project Management Institute (PMI). The series is designed p. cm .-(The PMBOK handbook series: v.no.6) to complement the Project Management Body of Knowledge (PMBOK) Includes bibliographical references. as codified by PMI. ISBN 1-880410-00-1 (10 vol. set).-ISBN 1-880410-06-0 (vo1.6) This handbook deals with the function of Risk Management in the 1. Industrial project management. 2. Risk management. I. Title. 11. Series. context of project or program management. It establishes the need for HD69.P76W54 1992 examining risks and opportunities in project work and describes ap- 658.4'04-dc20 92-3336 proaches which can lead to significant reduction of the risks as well as to CIP better project performance. This is a sometimes overlooked aspect of project management which can often result in significant improvements ISBN 1-880410-06-0 (Volume 6) in the ultimate success of the project. 1-880410-00-1 (10 Volume Set) This handbook should appeal equally to those who are looking for a summary of the basics of project and program risk management, as well as to those who are studying for PMI's certification program. In addition, the material in the handbook will benefit course developers, trainers and academics who are seeking guidance as to appropriate project and pro- gram risk management educational content. In keeping with previous practice, this first printing of the handbook is being made available as a "Preliminary Issue for Trial Use and Com- ment." Since the content is tied specifically to the PMBOK, it is important to ensure that PMI members support the material and its manner of presentation. I hope, therefore, that readers will take a moment to contrib- ute constructive suggestions for improving and upgrading the next issue Copyright 01992 by the Project Management Institute. All rights reserved. by completing and returning the Comments page at the end of this book. Printed in the United States of America. No part of this work may be reproduced or transmitted in any The material in this handbook has been assembled entirely by volun- form or by any means, electronic, manual, photocopying, recording, or by any information storage tary PMI member effort and, as anyone knows who has been involved in and retrieval system, without prior written permission of the publisher. similar undertakings, requires many hours of dedicated effort. In partic- ular I would like to acknowledge the efforts of Max Wideman and the "PMI" is a federally registered trade and service mark; "PMP" and the PMP logo are federally many people who provided comments and suggestions on the various registered certification marks; and the PMI logo, "PMBOK" and "Building professionalism in project drafts. To all those who contributed their thoughts and writings to this management." are trademarks of Project Management Institute. first issue, I express our appreciation for a job well done! PMI books are available at quantity discounts. For more information, please write to the Business Manager, PMI Publishing Division, Forty Colonial Square, Sylva, North Carolina, 28779 USA. Or Rodney J. Dawson contact your local bookstore. President, Project Management Institute The paper used in this book complies with the Permanent Paper Standard issued by the National Information Standards Organization (239.48-1984). Preface Acknowledgments Welcome to project and program risk management! Understandably, the risks associated with large and very large pro- In a very real sense, progress is made by spotting opportunities and jects have received noteworthy attention in the literature, because of the taking advantage of them. Once identified, the most aggressive way of taking substantial sums of money involved on the one hand, and the political advantage of such opportunities is by establishing a project. Thus, the whole and professional reputations of the sponsors on the other. On lesser point of a project is to introduce some change which wiU be beneficial in projects, however, aspects of the project which may be at risk are fre- financial or other ways to the sponsors and users of the project. quently submerged in an all-encompassing "contingency allowance" de- However, introducing change means introducing something new, to termined as a result of some previous experience. For many, this approach venture forth, to take some risks. So risks are the corollary of opportunity. They may be quite satisfactory, yet closer examination of the subject indicates represent exposure to mischance, hazards, and the possibility of adverse that including risk as a pro-active management function provides project consequences. They are the down-side of a prom undertaking. While pro* management with an added management opportunity. management is the best way of manapg opportunity, taking risks has always Project and Program Risk Management furnishes the chance to better been a fundamental part of the process, and this needs to be pro-actively understand the nature of the project at hand, to involve team members in managed through the function of Pro* and Program Risk Management. its strengths and weaknesses, and generally to integrate the core functions Generally, when we speak of taking a risk we tend to think of those of Scope, Quality, Time and Cost with the interactive functions of Human things which are at long odds, are highly chancy and possibly hazardous. Resources, Contract/Procurement, and lnformation/Communications Yet many risks we take in everyday life are so commonplace that we scarcely management. For these reasons, PMI early recognized the importance of gve them a thought. Instead, we treat them as mere uncertainties and react this subject to the overall success of a project, no matter what its size or to them subconsciously, taking precautions that experience has taught us are area of application, and so identified Project and Program Risk Manage- only prudent. ment as a separate PMBOK topic. However, in today's markets with more difficult economic conditions, Once again many PMI members, too numerous to cite all by name, tougher competition, and ever advancing technology, project uncertainty have enthusiastically volunteered material, suggestions and encourage- and risk have assumed sigruficantly greater proportions. Indeed, in most ment for the development of this handbook. I would, however, like to projects, not only are the uncertainties and risks numerous, but they are also mention a few who have been particular contributors or my mentors in interrelated. This affects project results in complex ways, making it difficult this effort: Mike Curran, David Hamburger, and Bill Hosley for most for management to be confident in forecasting the final results. helpful explanations, conversations and text; David Hulett for a copy of Therefore, Project and Program Risk Management is seen as the formal an excellent Orange County Chapter workshop handout on Risk Manage- process whereby the risks and opportunities are systematically identified, ment; Pat Buckley and Bill Duncan for a change in emphasis; Chris Quaife assessed and appropriately provided for in the course of project planning for both written contributions and thorough and perceptive comments on and implementation. It means taking a pro-active stance to cultivate an my original texts; and Davidson Frame for encouragement and testing the environment in which project and program risks are sigruficantlyreduced, handbook in one of his classes. I am sure that readers will benefit greatly if not eliminated entirely, and opportunities are cultivated. Project and from their work. Any errors of interpretation or omissions are, of course, Program Risk Management should encompass the full spectrum of activities my own responsibility. associated with the handling of project uncertainties. As always, my wife Audrey has been most supportive of this work As one of project management's integrative functions (see PMBOK and patiently endured through many hours of moans and groans arising Handbook Volume 1, A Framework for Projecf and Program Management from the effort of putting pen to paper (or more contemporarily, fingers Integration) Project and Program Risk Management is inextricably tied into to keyboard). each of the other project management functions, especially the four basic project constraints of Scope, Quabty, Time and Cost. It is, therefore, a key function of the project management process. However, management's atti- R. Max Wideman, Fellow, PMI Editor tude towards risk, in many cases, is governed by the extent of their under- standing of the risk management process, their confidence in the associated techniques and in the analyhcal results obtained. Others consider the subject too mathematical, yet many risks relate to people and their attitudes. Hence the need for this handbook iii Contents Chapter VI Risk Response and Documentation Response Options ............... VI .l Foreword
Recommended publications
  • Max Wideman, FCSCE, FEIC, FICE, FPMI, FCMI, Is a Globally-Recognized Author, Consultant and Expert
    Honorary Global Advisor – P/PM Profession Max Wideman Fellow, Former President & Chair, PMI Fellow, Institute of Civil Engineers (UK) Fellow, Engineering Institute of Canada Fellow, Canadian Society of Civil Engineers Fellow, Chartered Management Institute (UK) Ontario, Canada Max Wideman, FCSCE, FEIC, FICE, FPMI, FCMI, is a globally-recognized author, consultant and expert. He is widely recognized as one of the world’s leading authorities on modern project and program management. The Wideman PM Glossary is one of the most widely-referenced lexicons of PM terms and terminology in the world today. For those who wish to use it, with over 6,000 entries, it is available free on-line on his web site at www.wideman.com. There you will also find details of smaller but more up-to-date industry-dedicated versions available for download at very modest costs. Max’s personal website is one of the world’s best- known online resources for project and program management. Max Wideman has over 50 years of PM-related experience in a wide range of projects and industries. He is a registered professional engineer specializing in project management consulting. Max is a Fellow of the Institution of Civil Engineers (UK), a Fellow of the Engineering Institute of Canada, a Fellow of the Canadian Society of Civil Engineers, a Fellow of the Project Management Institute (PMI®) and a Fellow of the Chartered Management Institute (UK). Max served on the PMI Board of Directors as VP Member Services (1984), President (1987) and Chairman of the Board (1988). As Chairman of PMI's Standards Board, Max won PMI’s Distinguished Contribution Award in 1985 and Person of the Year Award in 1986.
    [Show full text]
  • Development of a Method to Improve the Definition and Alignment of Intangible Project Outcomes with Tangible Project Outputs Ke
    Development of a Method to Improve the Definition and Alignment of Intangible Project Outcomes with Tangible Project Outputs Kersti Nogeste Doctor of Project Management 2006 RMIT Development of a Method to Improve the Definition and Alignment of Intangible Project Outcomes with Tangible Project Outputs A thesis submitted in partial fulfilment of the requirements for the degree of Doctor of Project Management (DPM) Kersti Nogeste B.App.Sc., Dip.Ed., M.Bus. Graduate School of Business RMIT Business RMIT University April 2006 II Development of a Method to Improve the Definition and Alignment of Intangible Project Outcomes with Tangible Project Outputs DECLARATION I certify that except where due acknowledgement has been made, the work is that of the author alone; the work has not been submitted previously, in whole or in part, to qualify for any academic award; the content of the thesis is the result of work which has been carried out since the official commencement date of the approved research program; and, any editorial work, paid or unpaid, carried out by a third party is acknowledged. Kersti Nogeste April 2006 III Development of a Method to Improve the Definition and Alignment of Intangible Project Outcomes with Tangible Project Outputs ACKNOWLEDGEMENTS I wish to thank my supervisor Professor Derek Walker for his academic guidance, my parents for instilling in me the importance of education and my husband for his unstinting support. I also wish to recognise the cooperation received from an Australian Water Utility, the Victims Referral
    [Show full text]
  • Balancing Leadership and Management
    8230 Leesburg Pike, Suite 800 Vienna, VA 22182 (703) 790-9595 Fax: (703) 790-1371 www.managementconcepts.com Copyright © 2010 by Management Concepts, Inc. All rights reserved. No part of this book may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying, recording, or by an information storage and retrieval system, without permission in writing from the publisher, except for brief quotations in review articles. Printed in the United States of America Library of Congress Cataloging-in-Publication Data Weinstein, Jonathan. Achieving project management success in the federal government / Jonathan Weinstein, Timothy Jaques. p. cm. ISBN 978-1-56726-275-9 1. Public administration—United States. 2. Project management—United States. I. Jaques, Timothy, II. Title. JF1351.W45 2010 352.3′650973—dc22 2009048304 10 9 8 7 6 5 4 3 2 1 Preface We can’t solve problems by using the same kind of thinking we used when we created them. —ALBERT EINSTEIN Projects pervade our everyday work and life, and governments have dealt in the realm of projects since the beginning of recorded time. The U.S. federal government has employed project management since its earliest days and in recent years has begun the process of formalizing the methods it uses to carry out a wide-ranging spectrum of projects. Project management varies widely across the federal government. Our goal in this book is not to provide an exhaustive enumeration of project management practices, but rather to offer a realistic cross section of the project management discipline—a “state of the practice” in the largest single enterprise in the world, the U.S.
    [Show full text]
  • STATE of the ART of PROJECT MANAGEMENT: 2004 Russell D. Archibald, Fellow PMI and APM/IPMA, Msc, PMP ABSTRACT 1. PROJECT MANAGEM
    STATE OF THE ART OF PROJECT MANAGEMENT: 2004 Russell D. Archibald, Fellow PMI and APM/IPMA, MSc, PMP 2o Simposio di PM Project Manager Role Evolution Castlegandolfo (Roma), Italia 24 giugno 2004 ABSTRACT The practice of project management (PM) has evolved over half a century and permeates all industries, institutions and governments throughout the world. This paper conveys a picture of the state of the art in this management discipline in 2004, and provides some predictions of the direction of its continued evolution over the next five years. Four major subjects are covered: 1. PM Within Organizations 2. PM Applications, Practices, and Tools 3. PM and People 4. PM in the Next Five Years A global perspective is presented and briefly discussed for several topics under each of these subjects. 1. PROJECT MANAGEMENT WITHIN ORGANIZATIONS Three topics are discussed in this part: • Characteristics of PM: How does PM differ from managing functional organizations? • Projects, Programs, and Project Portfolios: Their classification and management needs • Organizational Capabilities and Maturity in PM: Assessing and improving PM capabilities CHARACTERISTICS OF PROJECT MANAGEMENT Projects exist in every type of human enterprise. They are unique, complex undertakings that create new products, facilities, services, and events, among other things, bring about major organizational and other desired changes or recovery from natural or man-made disasters. Projects have starting and ending points in time and progress through a number of life cycle phases. The discipline of project management has evolved because the more traditional, well-established industrial age principles and methods for managing our classical functional organizations (involving on- going, repetitive operations of various kinds) do not work well for planning, controlling, and managing projects, programs, or project portfolios.
    [Show full text]
  • Project Manager to Project Leader? and the Rocky Road Between
    Project Manager to Project Leader? and the Rocky Road Between... Vijay K. Verma, TRIUMF, University of British Columbia, and R. Max Wideman, FPMI, AEW Services, BC. (Revision 3, 06-11-02) The original version of this paper was presented at the Project Management Institute's 25th Annual Seminar & Symposium, held in Vancouver, BC, Canada, October 17, 1994. Introduction Issue: Is it Leadership or Management that is most needed for conducting projects in the 1990s and beyond? In recent years there has been a spate of publications on "Leadership" and “Team Building” by numerous authors such as Bennis, Drucker, Covey, Depree, Byham, McLean and Weitzel, Dilenschneider, Fisher, Batten and others. Much of this has been directed to the "Captains of North American Industry". However, in our opinion, leadership, management and team building, while all closely allied, are sufficiently different in the project environment that they require special study. The old image of a powerful project personality with a burning vision of the future state rounding up the troops and charging off to Nirvana, is hardly consistent with modern management thinking. Consequently, some of the current concepts of leadership and attributes required of the leader of an enterprise need to be carefully rethought when applied in the project context. That is, if a project is to succeed and be viewed as successful. So the question is: What sort of leadership or management is the most relevant to project management in the decade of the 1990s and beyond? Considering the extent of management literature published in recent years, it might be thought that this is no longer an issue.
    [Show full text]
  • Managing the Development of Building Projects for Better Results By: R.Max Wideman First Published in 1981, Updated for Web Presentation, December, 2000
    Managing the Development of Building Projects for Better Results By: R.Max Wideman First published in 1981, updated for web presentation, December, 2000 Introduction It is reasonable to assume that the objective of a building project is to create the best possible facility for a given level of expenditure. If this is true, then the objective of management during the development stage of the project should be to establish an effective project team, a unity of purpose and commitment to results. Yet the process of managing a project through the development phase is frequently not well understood by the principal players. And the dynamics of their separate interests may well run counter to the overall project objectives. Indeed, in North America the adversarial attitude amongst the various segments of the building industry is so entrenched that it is some times difficult to persuade the parties to the project to act together in the common interest. At least, not without good communication, or perhaps a gentle education program. So, the development manager, or project manager, must be aware of the dichotomies that exist and the pitfalls that he or she faces. This is the first step in understanding and improving the performance of the team and the resulting development process. Management and the Principal Parties The principal parties to a building project and their respective interests may be identified as follows: • The "Owner as Sponsor" anxious to maximize return on investment, perhaps at the expense of operational costs • The "Owner as Operator" anxious to minimize operating costs, perhaps at the expense of initial capital costs • The "Designer" anxious to provide a good design service and build a reputation for future work, perhaps by creating a “professional image” in the final building • The "Constructor" anxious to maximize profit, especially if severe market competition has resulted in tight firm-price margins • The "Project Manager" anxious to set the stage for a successful project implementation through efficient management.
    [Show full text]
  • Comparing PRINCE2 with Pmbok® R
    Comparing PRINCE2 with PMBoK® R. Max Wideman AEW Services, Vancouver, BC, Canada, 2002 Introduction From time to time we are asked to recommend project management systems and methodologies, or to compare them as part of some selection process. This month we have been taking an in-depth look at PRINCE2, a widely recognized de facto standard used extensively by the UK government and in the private sector.1 As a basis for comparison, and because we are located in North America, we will refer to the Project Management Institute's so-called "PMBOK" which actually refers to their publication "A Guide to the Project Management Body of Knowledge" (2000 Edition). "PRINCE" stands for Projects IN Controlled Environments and is described as a structured method for effective project management for all types of project, not just for information systems, although the influence of that industry is very clear in the methodology. The 2002 version has been through a number of incarnations in the past and is now the result of the "experience of scores of projects, project managers and project teams." The 408-page document, like the Guide (216 pages) is copyright, but the content is clearly generic common sense. The PRINCE2 Introduction lists a significant set of reasons why projects fail, and the methodology sets out to remove these causes. Figure 1 AEW Services, Vancouver, BC ©2002 Email: [email protected] Comparing PRINCE2 with PMBoK® Page 2 of 11 Figure 1 above shows the knowledge areas and processes of the Project Management Institute's Guide to PMBOK and Figure 2 below shows the comparable PRINCE2 content and usage.
    [Show full text]
  • History of the Société Franco-Anglaise De Cardiff from Its Foundation in 1906 Until 1995
    CENTENARY OF SOCIETE FRANCO-BRITANNIQUE DE CARDIFF 1906 - 2006 Arlette Ragody-Hughes and John Martin ENGLISH VERSION SOCIETE FRANCO-BRITANNIQUE DE CARDIFF CENTENARY OF SOCIETE FRANCO-BRITANNIQUE DE CARDIFF 1906 - 2006 Arlette Ragody-Hughes and John Martin Part 1: History of the Société Franco-Anglaise de Cardiff from its Foundation in 1906 until 1995 Part 2: Recent Activities of the Society Part 3: Appendices Acknowledgements. All illustrations, except where explicitly stated otherwise, are from the archives of the Society or its members. The generous help given by the staff of Cardiff Central Library, the Glamorgan Records Office and the National Museum of Wales is gratefully acknowledged. Cover illustrations: top left, original artwork from the programme for a meeting of the Society on 2 December 1911 drawn by Marcel Ragody, president of the Society in 1912; bottom right, photograph of members of the Society at Mont-Saint-Michel during the trip to France in June 1999. Part 1: The History of the Société Franco-Anglaise de Cardiff from its Foundation in 1906 until 1995 by Arlette Ragody-Hughes This is the text of a talk given to the Society in February 1999 by Arlette Ragody- Hughes, with contributions from Russell Jones. Arlette has had a long connection with the Society. She became a member of the Society in 1938, and served in many capacities including president in 1981-82 and 1982-83. Before that, her parents were closely associated with the Society. Her father, Marcel Ragody, was president as early as 1912 and again in 1947-49 and her mother was president in 1961-63.
    [Show full text]
  • Nternational Handbook of Academic Research and Teaching
    ISSN 2150-6906 nternational Handbook of Academic Research and Teaching 2010 Proceedings Volume 10 Published by: Intellectbase International Consortium . INTELLECTBASE INTERNATIONAL CONSORTIUM Academic Conference, Houston, TX, March 18-20, 2010 Intellectual Perspectives & Multi-Disciplinary Foundations Conference Proceedings Spring 2010 PROGRAM COMMITTEE Dr. David King Dr. Jifu Wang Conference Chair & Editor Conference Co-Chair Mrs. Karina Dyer Mr. Ben Murray Australian Affiliate & Senior Executive Web Manager & Research Associate CONFERENCE ORGANIZERS & INTERNATIONAL AFFILIATES United States Australia Europe Ms. Regina Beam Mrs. Karina Dyer Mr. Kevin Kofi Mr. Robert Edwards Mr. Graeme William Mr. Benjamin Effa Mrs. Erin Murray Ms. Michelle Joanne Ms. Christina Maame Ms. Loria Hampton Mrs. Wendy Morrell Mr. Kenneth Obeng www.intellectbase.org Published by Intellectbase International Consortium (IIC) Conference Committee: Intellectbase International Consortium, 1615 Seventh Avenue North, Nashville, TN 37208, USA ISSN (Print): 1940-1876 --------- Issued by the Library of Congress, Washington DC, USA ISSN (CD-ROM): 1940-1884 --------- Issued by the Library of Congress, Washington DC, USA ©2010. This volume is copyright to the Intellectbase International Consortium Academic Conferences. Apart from use as permitted under the Copyright Act of 1976, no part may be reproduced by any process without prior written permission. EXECUTIVE EDITORIAL BOARD (EEB) AND REVIEWERS TASK PANEL (RTP) Dr. David White Dr. Dennis Taylor Roosevelt University, USA RMIT University, Australia Dr. Danka Radulovic Dr. Harrison C. Hartman University of Belgrade, Serbia University of Georgia, USA Dr. Sloan T. Letman, III Dr. Sushil Misra American Intercontinental University, USA Concordia University, Canada Dr. Jiri Strouhal Dr. Avis Smith University of Economics-Prague, Czech Republic New York City College of Technology, USA Dr.
    [Show full text]
  • Optimizing Success by Matching Management Style to Project Type
    Optimizing Success by matching Management Style to Project Type The original of this paper first published on the PMForum web site, September, 2000. (Updated presentation, April, 2002) Aaron J. Shenhar, Institute Professor of Management, Stevens Institute of Technology, Hoboken, NJ. R. Max Wideman, FPMI, AEW Services, Vancouver, BC, Canada Introduction The purpose of this paper is to bring together the findings of the previous papers in this series to show a connecting thread that, if followed, leads to a better understanding of the project management process, and hence to higher levels of project success. This thread is summarized as follows · The meaning of project success · The nature of fundamentally different types of project · Their technological content · Their scope and degree of complexity · The nature of project work · Project leader personality traits and consequent management styles, and · Selection of most appropriate project leader for best chance of project success. But what is "project success", and how might such success be influenced by the particular type of project and how it is managed? Any serious discussion of the concepts of project management require that the terms to be used are clearly defined. While there is a general understanding of what a project is and what project management is about, there is no consensus amongst practitioners as to precise definitions of either of these terms. So we must start our journey by establishing what we mean by the terms we use for the purposes of this paper. For examples of different definitions in common use in each case, visit the PM Glossary and look up each term! Project and project management In the context of "project success", our preferred definition of project is as follows.
    [Show full text]
  • 29Th Annual Conference of the Canadian Society for Civil Engineering 2001
    29th Annual Conference of the Canadian Society for Civil Engineering 2001 2001: A Civil Odyssey Victoria, British Columbia, Canada 30 May – 2 June 2001 Volume 1 of 2 Editors: Don Noakes Maria Elektorowicz Brenda McCabe Ram Balachandar ISBN: 978-1-60423-315-5 Printed from e-media with permission by: Curran Associates, Inc. 57 Morehouse Lane Red Hook, NY 12571 Some format issues inherent in the e-media version may also appear in this print version. Copyright© (2001) by the Canadian Society for Civil Engineering All rights reserved. Printed by Curran Associates, Inc. (2014) For permission requests, please contact the Canadian Society for Civil Engineering at the address below. Canadian Society for Civil Engineering 4920 de Maisonneuve Blvd. W. Suite 201 Montréal, QC H3Z 1N1 Phone: (514) 933-2634 Fax: (514) 933-3504 [email protected] Additional copies of this publication are available from: Curran Associates, Inc. 57 Morehouse Lane Red Hook, NY 12571 USA Phone: 845-758-0400 Fax: 845-758-2634 Email: [email protected] Web: www.proceedings.com Table of Contents / Table des matières 29th Annual Conference 29e congrès annuel Design Considerations for New and Existing Airfield Pavements in Saudi A1 Arabia 1 Khalid Al-Ghunaim and Dolat S. Mehta Decision Support System for Facility Maintenance Management 9 A2 Maria Al-Hussein, Claude Bédard, and Sabah Alkass Development and Testing of a Miniature Cone Penetrometer Deployed from a A3 Horizontal Probe 18 E.N. Allouche and M. Devaux Lateral Seismic Behaviour of Tall Guyed Telecommunication Towers 25 A4 Gholamreza Ghodrati Amiri Evaluating CSO Screening Technologies for The City of Edmonton 33 A5 R.B.
    [Show full text]
  • The Role of the Project Life Cycle (Life Span) in Project Management a Literature Review by R
    2/1/04 The Role of the Project Life Cycle (Life Span) in Project Management A literature review by R. Max Wideman (Updated February, 2004.) Introduction Patel and Morris have stated that "The life cycle is the only thing that uniquely distinguishes projects from non-projects".1 If that is true, then it would be valuable to examine just what role the so-called project life cycle plays in the conduct of project management. And, moreover, has this changed over the years as we improve our understanding of the complexities of project management. So, what is the project life cycle? According to the same source "The sequence of phases through which the project will evolve. It is absolutely fundamental to the management of projects . It will significantly affect how the project is structured. The basic life cycle follows a common generic sequence: Opportunity, Design & Development, Production, Hand-over, and Post-Project Evaluation. The exact wording varies between industries and organizations. There should be evaluation and approval points between phases often termed 'gates'."2 How does that make it different from normal operational corporate endeavors? For that we must understand the definition of project. According to Richard E. Westney: "A project can be defined as the work required to take an opportunity and convert it into an asset."3 In this sense, both the opportunity and asset are singular, with the implied use being for generating benefit – rather than consumed as a resource in normal operational activity over a prolonged period. The Patel and Morris definition refers to "gates" between phases.
    [Show full text]