PMBOK Guide 6th Edition PDF

 A Guide to the PROJECT MANAGEMENT BODY OF KNOWLEDGE (PMBOK® GUIDE)...

 A Guide to the PROJECT MANAGEMENT BODY OF KNOWLEDGE (PMBOK® GUIDE) Sixth Edition This book was printed utilizing a patented anti-counterfeit print technology designed to prevent unauthorized reproductions. The paper color is gray instead of white. When the pages of the book are copied or scanned a hidden warning message will appear in the background. This security feature is intended to discourage anyone from attempting to illegally reproduce or counterfeit this book. Library of Congress Cataloging-in-Publication Data Names: Project Management Institute, publisher. Title: A guide to the project management body of knowledge (PMBOK guide) / Project Management Institute. Other titles: PMBOK guide Description: Sixth edition. | Newtown Square, PA: Project Management Institute, 2017. | Series: PMBOK guide | Includes bibliographical references and index. Identifiers: LCCN 2017032505 (print) | LCCN 2017035597 (ebook) | ISBN 9781628253900 (ePUP) | ISBN 9781628253917 (kindle) | ISBN 9781628253924 ( Web PDF) | ISBN 9781628251845 (paperback) Subjects: LCSH: Project management. | BISAC: BUSINESS & ECONOMICS / Project Management. Classification: LCC HD69.P75 (ebook) | LCC HD69.P75 G845 2017 (print) | DDC 658.4/04--dc23 LC record available at https://lccn.loc.gov/2017032505 ISBN: 978-1-62825-184-5 Published by: Project Management Institute, Inc. 14 Campus Boulevard Newtown Square, Pennsylvania 19073-3299 USA Phone: +1 610-356-4600 Fax: +1 610-356-4647 Email: [email protected] Website: www.PMI.org ©2017 Project Management Institute, Inc. All rights reserved. Project Management Institute, Inc. content is copyright protected by U.S. intellectual property law that is recognized by most countries. To republish or reproduce PMI's content, you must obtain our permission. Please go to http://www.pmi.org/permissions for details. To place a Trade Order or for pricing information, please contact Independent Publishers Group: Independent Publishers Group Order Department 814 North Franklin Street Chicago, IL 60610 USA Phone: +1 800-888-4741 Fax: +1 312- 337-5985 Email: [email protected] (For orders only) For all other inquiries, please contact the PMI Book Service Center. PMI Book Service Center P.O. Box 932683, Atlanta, GA 31193-2683 USA Phone: 1-866-276-4764 (within the U.S. or Canada) or +1-770-280-4129 (globally) Fax: +1-770-280-4113 Email: [email protected] Printed in the United States of America. No part of this work may be reproduced or transmitted in any form or by any means, electronic, manual, photocopying, recording, or by any information storage and retrieval system, without prior written permission of the publisher. The paper used in this book complies with the Permanent Paper Standard issued by the National Information Standards Organization (Z39.48 —1984). PMI, the PMI logo, PMBOK, OPM3, PMP, CAPM, PgMP, PfMP, PMI-RMP, PMI-SP, PMI-ACP, PMI-PBA, PROJECT MANAGEMENT JOURNAL, PM NETWORK, PMI TODAY, PULSE OF THE PROFESSION and the slogan MAKING PROJECT MANAGEMENT INDISPENSABLE FOR BUSINESS RESULTS. are all marks of Project Management Institute, Inc. For a comprehensive list of PMI trademarks, contact the PMI Legal Department. All other trademarks, service marks, trade names, trade dress, product names and logos appearing herein are the property of their respective owners. Any rights not expressly granted herein are reserved. 10 9 8 7 6 5 4 3 2 1 NOTICE The Project Management Institute, Inc. (PMI) standards and guideline publications, of which the document contained herein is one, are developed through a voluntary consensus standards development process. This process brings together volunteers and/or seeks out the views of persons who have an interest in the topic covered by this publication. While PMI administers the process and establishes rules to promote fairness in the development of consensus, it does not write the document and it does not independently test, evaluate, or verify the accuracy or completeness of any information or the soundness of any judgments contained in its standards and guideline publications. PMI disclaims liability for any personal injury, property or other damages of any nature whatsoever, whether special, indirect, consequential or compensatory, directly or indirectly resulting from the publication, use of application, or reliance on this document. PMI disclaims and makes no guaranty or warranty, expressed or implied, as to the accuracy or completeness of any information published herein, and disclaims and makes no warranty that the information in this document will fulfill any of your particular purposes or needs. PMI does not undertake to guarantee the performance of any individual manufacturer or seller's products or services by virtue of this standard or guide. In publishing and making this document available, PMI is not undertaking to render professional or other services for or on behalf of any person or entity, nor is PMI undertaking to perform any duty owed by any person or entity to someone else. Anyone using this document should rely on his or her own independent judgment or, as appropriate, seek the advice of a competent professional in determining the exercise of reasonable care in any given circumstances. Information and other standards on the topic covered by this publication may be available from other sources, which the user may wish to consult for additional views or information not covered by this publication. PMI has no power, nor does it undertake to police or enforce compliance with the contents of this document. PMI does not certify, test, or inspect products, designs, or installations for safety or health purposes. Any certification or other statement of compliance with any health or safety-related information in this document shall not be attributable to PMI and is solely the responsibility of the certifier or maker of the statement. TABLE OF CONTENTS PART 1. A GUIDE TO THE PROJECT MANAGEMENT BODY OF KNOWLEDGE (PMBOK® Guide) 1. INTRODUCTION 1.1 Overview and Purpose of this Guide 1.1.1 The Standard for Project Management 1.1.2 Common Vocabulary 1.1.3 Code of Ethics and Professional Conduct 1.2 Foundational Elements 1.2.1 Projects 1.2.2 The Importance of Project Management 1.2.3 Relationship of Project, Program, Portfolio, and Operations Management 1.2.4 Components of the Guide 1.2.5 Tailoring 1.2.6 Project Management Business Documents 2. THE ENVIRONMENT IN WHICH PROJECTS OPERATE 2.1 Overview 2.2 Enterprise Environmental Factors 2.2.1 EEFs Internal to the Organization 2.2.2 EEFs External to the Organization 2.3 Organizational Process Assets 2.3.1 Processes, Policies, and Procedures 2.3.2 Organizational Knowledge Repositories 2.4 Organizational Systems 2.4.1 Overview 2.4.2 Organizational Governance Frameworks 2.4.3 Management Elements 2.4.4 Organizational Structure Types 3. THE ROLE OF THE PROJECT MANAGER  3.1 Overview 3.2 Definition of a Project Manager 3.3 The Project Manager's Sphere of Influence 3.3.1 Overview 3.3.2 The Project 3.3.3 The Organization 3.3.4 The Industry 3.3.5 Professional Discipline 3.3.6 Across Disciplines 3.4 Project Manager Competences 3.4.1 Overview 3.4.2 Technical Project Management Skills 3.4.3 Strategic and Business Management Skills 3.4.4 Leadership Skills 3.4.5 Comparison of Leadership and Management 3.5 Performing Integration 3.5.1 Performing Integration at the Process Level 3.5.2 Integration at the Cognitive Level 3.5.3 Integration at the Context Level 3.5.4 Integration and Complexity 4. PROJECT INTEGRATION MANAGEMENT 4.1 Develop Project Charter 4.1.1 Develop Project Charter: Inputs 4.1.2 Develop Project Charter: Tools and Techniques 4.1.3 Develop Project Charter: Outputs 4.2 Develop Project Management Plan 4.2.1 Develop Project Management Plan: Inputs 4.2.2 Develop Project Management Plan: Tools and Techniques 4.2.3 Develop Project Management Plan: Outputs 4.3 Direct and Manage Project Work 4.3.1 Direct and Manage Project Work: Inputs 4.3.2 Direct and Manage Project Work: Tools and Techniques 4.3.3 Direct and Manage Project Work: Outputs  4.4 Manage Project Knowledge 4.4.1 Manage Project Knowledge: Inputs 4.4.2 Manage Project Knowledge: Tools and Techniques 4.4.3 Manage Project Knowledge: Outputs 4.5 Monitor and Control Project Work 4.5.1 Monitor and Control Project Work: Inputs 4.5.2 Monitor and Control Project Work: Tools and Techniques 4.5.3 Monitor and Control Project Work: Outputs 4.6 Perform Integrated Change Control 4.6.1 Perform Integrated Change Control: Inputs 4.6.2 Perform Integrated Change Control: Tools and Techniques 4.6.3 Perform Integrated Change Control: Outputs 4.7 Close Project or Phase 4.7.1 Close Project or Phase: Inputs 4.7.2 Close Project or Phase: Tools and Techniques 4.7.3 Close Project or Phase: Outputs 5. PROJECT SCOPE MANAGEMENT 5.1 Plan Scope Management 5.1.1 Plan Scope Management: Inputs 5.1.2 Plan Scope Management: Tools and Techniques 5.1.3 Plan Scope Management: Outputs 5.2 Collect Requirements 5.2.1 Collect Requirements: Inputs 5.2.2 Collect Requirements: Tools and Techniques 5.2.3 Collect Requirements: Outputs 5.3 Define Scope 5.3.1 Define Scope: Inputs 5.3.2 Define Scope: Tools and Techniques 5.3.3 Define Scope: Outputs 5.4 Create WBS 5.4.1 Create WBS: Inputs 5.4.2 Create WBS: Tools and Techniques 5.4.3 Create WBS: Outputs 5.5 Validate Scope  5.5.1 Validate Scope: Inputs 5.5.2 Validate Scope: Tools and Techniques 5.5.3 Validate Scope: Outputs 5.6 Control Scope 5.6.1 Control Scope: Inputs 5.6.2 Control Scope: Tools and Techniques 5.6.3 Control Scope: Outputs 6. PROJECT SCHEDULE MANAGEMENT 6.1 Plan Schedule Management 6.1.1 Plan Schedule Management: Inputs 6.1.2 Plan Schedule Management: Tools and Techniques 6.1.3 Plan Schedule Management: Outputs 6.2 Define Activities 6.2.1 Define Activities: Inputs 6.2.2 Define Activities: Tools and Techniques 6.2.3 Define Activities: Outputs 6.3 Sequence Activities 6.3.1 Sequence Activities: Inputs 6.3.2 Sequence Activities: Tools and Techniques 6.3.3 Sequence Activities: Outputs 6.4 Estimate Activity Durations 6.4.1 Estimate Activity Durations: Inputs 6.4.2 Estimate Activity Durations: Tools and Techniques 6.4.3 Estimate Activity Durations: Outputs 6.5 Develop Schedule 6.5.1 Develop Schedule: Inputs 6.5.2 Develop Schedule: Tools and Techniques 6.5.3 Develop Schedule: Outputs 6.6 Control Schedule 6.6.1 Control Schedule: Inputs 6.6.2 Control Schedule: Tools and Techniques 6.6.3 Control Schedule: Outputs 7. PROJECT COST MANAGEMENT  7.1 Plan Cost Management 7.1.1 Plan Cost Management: Inputs 7.1.2 Plan Cost Management: Tools and Techniques 7.1.3 Plan Cost Management: Outputs 7.2 Estimate Costs 7.2.1 Estimate Costs: Inputs 7.2.2 Estimate Costs: Tools and Techniques 7.2.3 Estimate Costs: Outputs 7.3 Determine Budget 7.3.1 Determine Budget: Inputs 7.3.2 Determine Budget: Tools and Techniques 7.3.3 Determine Budget: Outputs 7.4 Control Costs 7.4.1 Control Costs: Inputs 7.4.2 Control Costs: Tools and Techniques 7.4.3 Control Costs: Outputs 8. PROJECT QUALITY MANAGEMENT 8.1 Plan Quality Management 8.1.1 Plan Quality Management: Inputs 8.1.2 Plan Quality Management: Tools and Techniques 8.1.3 Plan Quality Management: Outputs 8.2 Manage Quality 8.2.1 Manage Quality: Inputs 8.2.2 Manage Quality: Tools and Techniques 8.2.3 Manage Quality: Outputs 8.3 Control Quality 8.3.1 Control Quality: Inputs 8.3.2 Control Quality: Tools and Techniques 8.3.3 Control Quality: Outputs 9. PROJECT RESOURCE MANAGEMENT 9.1 Plan Resource Management 9.1.1 Plan Resource Management: Inputs 9.1.2 Plan Resource Management: Tools and Techniques  9.1.3 Plan Resource Management: Outputs 9.2 Estimate Activity Resources 9.2.1 Estimate Activity Resources: Inputs 9.2.2 Estimate Activity Resources: Tools and Techniques 9.2.3 Estimate Activity Resources: Outputs 9.3 Acquire Resources 9.3.1 Acquire Resources: Inputs 9.3.2 Acquire Resources: Tools and Techniques 9.3.3 Acquire Resources: Outputs 9.4 Develop Team 9.4.1 Develop Team: Inputs 9.4.2 Develop Team: Tools and Techniques 9.4.3 Develop Team: Outputs 9.5 Manage Team 9.5.1 Manage Team: Inputs 9.5.2 Manage Team: Tools and Techniques 9.5.3 Manage Team: Outputs 9.6 Control Resources 9.6.1 Control Resources: Inputs 9.6.2 Control Resources: Tools and Techniques 9.6.3 Control Resources: Outputs 10. PROJECT COMMUNICATIONS MANAGEMENT 10.1 Plan Communications Management 10.1.1 Plan Communications Management: Inputs 10.1.2 Plan Communications Management: Tools and Techniques 10.1.3 Plan Communications Management: Outputs 10.2 Manage Communications 10.2.1 Manage Communications: Inputs 10.2.2 Manage Communications: Tools and Techniques 10.2.3 Manage Communications: Outputs 10.3 Monitor Communications 10.3.1 Monitor Communications: Inputs 10.3.2 Monitor Communications: Tools and Techniques 10.3.3 Monitor Communications: Outputs 11. PROJECT RISK MANAGEMENT 11.1 Plan Risk Management 11.1.1 Plan Risk Management: Inputs 11.1.2 Plan Risk Management: Tools and Techniques 11.1.3 Plan Risk Management: Outputs 11.2 Identify Risks 11.2.1 Identify Risks: Inputs 11.2.2 Identify Risks: Tools and Techniques 11.2.3 Identify Risks: Outputs 11.3 Perform Qualitative Risk Analysis 11.3.1 Perform Qualitative Risk Analysis: Inputs 11.3.2 Perform Qualitative Risk Analysis: Tools and Techniques 11.3.3 Perform Qualitative Risk Analysis: Outputs 11.4 Perform Quantitative Risk Analysis 11.4.1 Perform Quantitative Risk Analysis: Inputs 11.4.2 Perform Quantitative Risk Analysis: Tools and Techniques 11.4.3 Perform Quantitative Risk Analysis: Outputs 11.5 Plan Risk Responses 11.5.1 Plan Risk Responses: Inputs 11.5.2 Plan Risk Responses: Tools and Techniques 11.5.3 Plan Risk Responses: Outputs 11.6 Implement Risk Responses 11.6.1 Implement Risk Responses: Inputs 11.6.2 Implement Risk Responses: Tools and Techniques 11.6.3 Implement Risk Responses: Outputs 11.7 Monitor Risks 11.7.1 Monitor Risks: Inputs 11.7.2 Monitor Risks: Tools and Techniques 11.7.3 Monitor Risks: Outputs 12. PROJECT PROCUREMENT MANAGEMENT 12.1 Plan Procurement Management 12.1.1 Plan Procurement Management: Inputs 12.1.2 Plan Procurement Management: Tools and Techniques  12.1.3 Plan Procurement Management: Outputs 12.2 Conduct Procurements 12.2.1 Conduct Procurements: Inputs 12.2.2 Conduct Procurements: Tools and Techniques 12.2.3 Conduct Procurements: Outputs 12.3 Control Procurements 12.3.1 Control Procurements: Inputs 12.3.2 Control Procurements: Tools and Techniques 12.3.3 Control Procurements: Outputs 13. PROJECT STAKEHOLDER MANAGEMENT 13.1 Identify Stakeholders 13.1.1 Identify Stakeholders: Inputs 13.1.2 Identify Stakeholders: Tools and Techniques 13.1.3 Identify Stakeholders: Outputs 13.2 Plan Stakeholder Engagement 13.2.1 Plan Stakeholder Engagement: Inputs 13.2.2 Plan Stakeholder Engagement: Tools and Techniques 13.2.3 Plan Stakeholder Engagement: Outputs 13.3 Manage Stakeholder Engagement 13.3.1 Manage Stakeholder Engagement: Inputs 13.3.2 Manage Stakeholder Engagement: Tools and Techniques 13.3.3 Manage Stakeholder Engagement: Outputs 13.4 Monitor Stakeholder Engagement 13.4.1 Monitor Stakeholder Engagement: Inputs 13.4.2 Monitor Stakeholder Engagement: Tools and Techniques 13.4.3 Monitor Stakeholder Engagement: Outputs REFERENCES PART 2. THE STANDARD FOR PROJECT MANAGEMENT 1. INTRODUCTION 1.1 Projects and Project Management 1.2 Relationships Among Portfolios, Programs, and Projects 1.3 Linking Organizational Governance and Project Governance  1.4 Project Success and Benefits Management 1.5 The Project Life Cycle 1.6 Project Stakeholders 1.7 Role of the Project Manager 1.8 Project Management Knowledge Areas 1.9 Project Management Process Groups 1.10 Enterprise Environmental Factors and Organizational Process Assets 1.11 Tailoring the Project Artifacts 2. INITIATING PROCESS GROUP 2.1 Develop Project Charter 2.2 Identify Stakeholders 2.2.1 Project Management Plan Components 2.2.2 Project Documents Examples 2.2.3 Project Management Plan Updates 2.2.4 Project Documents Updates 3. PLANNING PROCESS GROUP 3.1 Develop Project Management Plan 3.2 Plan Scope Management 3.2.1 Project Management Plan Components 3.3 Collect Requirements 3.3.1 Project Management Plan Components 3.3.2 Project Documents Examples 3.4 Define Scope 3.4.1 Project Management Plan Components 3.4.2 Project Documents Examples 3.4.3 Project Documents Updates 3.5 Create WBS 3.5.1 Project Management Plan Components 3.5.2 Project Documents Examples 3.5.3 Project Documents Updates 3.6 Plan Schedule Management 3.6.1 Project Management Plan Components 3.7 Define Activities  3.7.1 Project Management Plan Components 3.7.2 Project Management Plan Updates 3.8 Sequence Activities 3.8.1 Project Management Plan Components 3.8.2 Project Documents Examples 3.8.3 Project Documents Updates 3.9 Estimate Activity Durations 3.9.1 Project Management Plan Components 3.9.2 Project Documents Examples 3.9.3 Project Documents Updates 3.10 Develop Schedule 3.10.1 Project Management Plan Components 3.10.2 Project Documents Examples 3.10.3 Project Management Plan Updates 3.10.4 Project Documents Updates 3.11 Plan Cost Management 3.11.1 Project Management Plan Components 3.12 Estimate Costs 3.12.1 Project Management Plan Components 3.12.2 Project Documents Examples 3.12.3 Project Documents Updates 3.13 Determine Budget 3.13.1 Project Management Plan Components 3.13.2 Project Documents Examples 3.13.3 Project Documents Updates 3.14 Plan Quality Management 3.14.1 Project Management Plan Components 3.14.2 Project Documents Examples 3.14.3 Project Management Plan Updates 3.14.4 Project Documents Updates 3.15 Plan Resource Management 3.15.1 Project Management Plan Components 3.15.2 Project Documents 3.15.3 Project Documents Updates 3.16 Estimate Activity Resources 3.16.1 Project Management Plan Components 3.16.2 Project Documents Examples 3.16.3 Project Documents Updates 3.17 Plan Communications Management 3.17.1 Project Management Plan Components 3.17.2 Project Documents Examples 3.17.3 Project Management Plan Updates 3.17.4 Project Documents Updates 3.18 Plan Risk Management 3.18.1 Project Management Plan Components 3.18.2 Project Documents Examples 3.19 Identify Risks 3.19.1 Project Management Plan Components 3.19.2 Project Documents Examples 3.19.3 Project Documents Updates 3.20 Perform Qualitative Risk Analysis 3.20.1 Project Management Plan Components 3.20.2 Project Documents Examples 3.20.3 Project Documents Updates 3.21 Perform Quantitative Risk Analysis 3.21.1 Project Management Plan Components 3.21.2 Project Documents Examples 3.21.3 Project Documents Updates 3.22 Plan Risk Responses 3.22.1 Project Management Plan Components 3.22.2 Project Documents Examples 3.22.3 Project Management Plan Updates 3.22.4 Project Documents Updates 3.23 Plan Procurement Management 3.23.1 Project Management Plan Components 3.23.2 Project Documents Examples 3.23.3 Project Documents Updates 3.24 Plan Stakeholder Engagement  3.24.1 Project Management Plan Components 3.24.2 Project Documents Examples 4. EXECUTING PROCESS GROUP 4.1 Direct and Manage Project Work 4.1.1 Project Management Plan Components 4.1.2 Project Documents Examples 4.1.3 Project Management Plan Updates 4.1.4 Project Documents Updates 4.2 Manage Project Knowledge 4.2.1 Project Management Plan Components 4.2.2 Project Documents 4.2.3 Project Management Plan Updates 4.3 Manage Quality 4.3.1 Project Management Plan Components 4.3.2 Project Documents Examples 4.3.3 Project Management Plan Updates 4.3.4 Project Documents Updates 4.4 Acquire Resources 4.4.1 Project Management Plan Components 4.4.2 Project Documents Examples 4.4.3 Project Management Plan Updates 4.4.4 Project Documents Updates 4.5 Develop Team 4.5.1 Project Management Plan Components 4.5.2 Project Documents Examples 4.5.3 Project Management Plan Updates 4.5.4 Project Documents Updates 4.6 Manage Team 4.6.1 Project Management Plan Components 4.6.2 Project Documents Examples 4.6.3 Project Management Plan Updates 4.6.4 Project Documents Updates 4.7 Manage Communications 4.7.1 Project Management Plan Components  4.7.2 Project Documents Example 4.7.3 Project Management Plan Updates 4.7.4 Project Documents Updates 4.8 Implement Risk Responses 4.8.1 Project Management Plan Components 4.8.2 Project Documents Examples 4.8.3 Project Documents Updates 4.9 Conduct Procurements 4.9.1 Project Management Plan Components 4.9.2 Project Documents Examples 4.9.3 Project Management Plan Updates 4.9.4 Project Documents Updates 4.10 Manage Stakeholder Engagement 4.10.1 Project Management Plan Components 4.10.2 Project Documents Examples 4.10.3 Project Management Plan Updates 4.10.4 Project Documents Updates 5. MONITORING AND CONTROLLING PROCESS GROUP 5.1 Monitor and Control Project Work 5.1.1 Project Management Plan Components 5.1.2 Project Documents Examples 5.1.3 Project Management Plan Updates 5.1.4 Project Documents Updates 5.2 Perform Integrated Change Control 5.2.1 Project Management Plan Components 5.2.2 Project Documents Examples 5.2.3 Project Management Plan Updates 5.2.4 Project Documents Updates 5.3 Validate Scope 5.3.1 Project Management Plan Components 5.3.2 Project Documents Examples 5.3.3 Project Documents Updates 5.4 Control Scope  5.4.1 Project Management Plan Components 5.4.2 Project Documents Examples 5.4.3 Project Management Plan Updates 5.4.4 Project Documents Updates 5.5 Control Schedule 5.5.1 Project Management Plan Components 5.5.2 Project Documents Examples 5.5.3 Project Management Plan Updates 5.5.4 Project Documents Updates 5.6 Control Costs 5.6.1 Project Management Plan Components 5.6.2 Project Documents Examples 5.6.3 Project Management Plan Updates 5.6.4 Project Documents Updates 5.7 Control Quality 5.7.1 Project Management Plan Components 5.7.2 Project Documents Examples 5.7.3 Project Management Plan Updates 5.7.4 Project Documents Updates 5.8 Control Resources 5.8.1 Project Management Plan Components 5.8.2 Project Documents Examples 5.8.3 Project Management Plan Updates 5.8.4 Project Documents Updates 5.9 Monitor Communications 5.9.1 Project Management Plan Components 5.9.2 Project Documents Examples 5.9.3 Project Management Plan Updates 5.9.4 Project Documents Updates 5.10 Monitor Risks 5.10.1 Project Management Plan Components 5.10.2 Project Documents Examples 5.10.3 Project Management Plan Updates 5.10.4 Project Documents Updates  5.11 Control Procurements 5.11.1 Project Management Plan Components 5.11.2 Project Documents Examples 5.11.3 Project Management Plan Updates 5.11.4 Project Documents Updates 5.12 Monitor Stakeholder Engagement 5.12.1 Project Management Plan Components 5.12.2 Project Documents Examples 5.12.3 Project Management Plan Updates 5.12.4 Project Documents Updates 6. CLOSING PROCESS GROUP 6.1 Close Project or Phase 6.1.1 Project Management Plan Components 6.1.2 Project Documents Examples 6.1.3 Project Documents Updates PART 3. APPENDICES, GLOSSARY, AND INDEX APPENDIX X1 SIXTH EDITION CHANGES APPENDIX X2 CONTRIBUTORS AND REVIEWERS OF THE PMBOK® GUIDE—SIXTH EDITION APPENDIX X3 AGILE, ITERATIVE, ADAPTIVE, AND HYBRID PROJECT ENVIRONMENTS APPENDIX X4 SUMMARY OF KEY CONCEPTS FOR KNOWLEDGE AREAS APPENDIX X5 SUMMARY OF TAILORING CONSIDERATIONS FOR KNOWLEDGE AREAS APPENDIX X6 TOOLS AND TECHNIQUES GLOSSARY LIST OF TABLES AND FIGURES PART 1. A GUIDE TO THE PROJECT MANAGEMENT BODY OF KNOWLEDGE (PMBOK® Guide) Figure 1-1. Organizational State Transition via a Project Figure 1-2. Project Initiation Context Figure 1-3. Portfolio, Programs, Projects, and Operations Figure 1-4. Organizational Project Management Figure 1-5. Interrelationship of PMBOK® Guide Key Components in Projects Figure 1-6. Example Process: Inputs, Tools & Techniques, and Outputs Figure 1-7. Project Data, Information, and Report Flow Interrelationship of Needs Assessment and Critical Figure 1-8. Business/Project Documents Figure 2-1. Project Influences Figure 3-1. Example of Project Manager's Sphere of Influence Figure 3-2. The PMI Talent Triangle® Figure 4-1. Project Integration Management Overview Develop Project Charter: Inputs, Tools & Techniques, and Figure 4-2. Outputs Figure 4-3. Develop Project Charter: Data Flow Diagram Develop Project Management Plan: Inputs, Tools & Techniques, Figure 4-4. and Outputs Figure 4-5. Develop Project Management Plan: Data Flow Diagram Direct and Manage Project Work: Inputs, Tools & Techniques, Figure 4-6. and Outputs Figure 4-7. Direct and Manage Project Work: Data Flow Diagram Manage Project Knowledge: Inputs, Tools & Techniques, and Figure 4-8. Outputs Figure 4-9. Manage Project Knowledge: Data Flow Diagram Monitor and Control Project Work: Inputs, Tools & Techniques, Figure 4-10. and Outputs Figure 4-11. Monitor and Control Project Work: Data Flow Diagram Figure 4-12. Perform Integrated Change Control: Inputs, Tools & Techniques, and Outputs Figure 4-13. Perform Integrated Change Control: Data Flow Diagram Figure 4-14. Close Project or Phase: Inputs, Tools & Techniques, and Outputs Figure 4-15. Close Project or Phase: Data Flow Diagram Figure 5-1. Project Scope Management Overview Plan Scope Management: Inputs, Tools & Techniques, and Figure 5-2. Outputs Figure 5-3. Plan Scope Management: Data Flow Diagram Figure 5-4. Collect Requirements: Inputs, Tools & Techniques, and Outputs Figure 5-5. Collect Requirements: Data Flow Diagram Figure 5-6. Context Diagram Figure 5-7. Example of a Requirements Traceability Matrix Figure 5-8. Define Scope: Inputs, Tools & Techniques, and Outputs Figure 5-9. Define Scope: Data Flow Diagram Figure 5-10. Create WBS: Inputs, Tools & Techniques, and Outputs Figure 5-11. Create WBS: Data Flow Diagram Figure 5-12. Sample WBS Decomposed Down Through Work Packages Figure 5-13. Sample WBS Organized by Phase Figure 5-14. Sample WBS with Major Deliverables Figure 5-15. Validate Scope: Inputs, Tools & Techniques, and Outputs Figure 5-16. Validate Scope: Data Flow Diagram Figure 5-17. Control Scope: Inputs, Tools & Techniques, and Outputs Figure 5-18. Control Scope: Data Flow Diagram Figure 6-1. Project Schedule Management Overview Figure 6-2. Scheduling Overview Plan Schedule Management: Inputs, Tools & Techniques, and Figure 6-3. Outputs Figure 6-4. Plan Schedule Management: Data Flow Diagram Figure 6-5. Define Activities: Inputs, Tools & Techniques, and Outputs Figure 6-6. Define Activities: Data Flow Diagram Figure 6-7. Sequence Activities: Inputs, Tools & Techniques, and Outputs Figure 6-8. Sequence Activities: Data Flow Diagram Figure 6-9. Precedence Diagramming Method (PDM) Relationship Types Figure 6-10. Examples of Lead and Lag Figure 6-11. Project Schedule Network Diagram Estimate Activity Durations: Inputs, Tools & Techniques, and Figure 6-12. Outputs Figure 6-13. Estimate Activity Durations: Data Flow Diagram Figure 6-14. Develop Schedule: Inputs, Tools & Techniques, and Outputs Figure 6-15. Develop Schedule: Data Flow Diagram Figure 6-16. Example of Critical Path Method Figure 6-17. Resource Leveling Figure 6-18. Example Probability Distribution of a Target Milestone Figure 6-19. Schedule Compression Comparison Relationship Between Product Vision, Release Planning, and Figure 6-20. Iteration Planning Figure 6-21. Project Schedule Presentations—Examples Figure 6-22. Control Schedule: Inputs, Tools & Techniques, and Outputs Figure 6-23. Control Schedule: Data Flow Diagram Figure 6-24. Iteration Burndown Chart Figure 7-1. Project Cost Management Overview Figure 7-2. Plan Cost Management: Inputs, Tools & Techniques, and Outputs Figure 7-3. Plan Cost Management: Data Flow Diagram Figure 7-4. Estimate Costs: Inputs, Tools & Techniques, and Outputs Figure 7-5. Estimate Costs: Data Flow Diagram Figure 7-6. Determine Budget: Inputs, Tools & Techniques, and Outputs Figure 7-7. Determine Budget: Data Flow Diagram Figure 7-8. Project Budget Components Figure 7-9. Cost Baseline, Expenditures, and Funding Requirements Figure 7-10. Control Costs: Inputs, Tools & Techniques, and Outputs Figure 7-11. Control Costs: Data Flow Diagram Figure 7-12. Earned Value, Planned Value, and Actual Costs Figure 7-13. To-Complete Performance Index (TCPI) Figure 8-1. Project Quality Management Overview Figure 8-2. Major Project Quality Management Process Interrelations Plan Quality Management: Inputs, Tools & Techniques, and Figure 8-3. Outputs Figure 8-4. Plan Quality Management: Data Flow Diagram Figure 8-5. Cost of Quality Figure 8-6. The SIPOC Model Figure 8-7. Manage Quality: Inputs, Tools & Techniques, and Outputs Figure 8-8. Manage Quality: Data Flow Diagram Figure 8-9. Cause-and-Effect Diagram Figure 8-10. Control Quality: Inputs, Tools & Techniques, and Outputs Figure 8-11. Control Quality: Data Flow Diagram Figure 8-12. Check Sheets Figure 9-1. Project Resource Management Overview Plan Resource Management: Inputs, Tools & Techniques, and Figure 9-2. Outputs Figure 9-3. Plan Resource Management: Data Flow Diagram Figure 9-4. Sample RACI Chart Estimate Activity Resources: Inputs, Tools & Techniques, and Figure 9-5. Outputs Figure 9-6. Estimate Activity Resources: Data Flow Diagram Figure 9-7. Sample Resource Breakdown Structure Figure 9-8. Acquire Resources: Inputs, Tools & Techniques, and Outputs Figure 9-9. Acquire Resources: Data Flow Diagram Figure 9-10. Develop Team: Inputs, Tools & Techniques, and Outputs Figure 9-11. Develop Team: Data Flow Diagram Figure 9-12. Manage Team: Inputs, Tools & Techniques, and Outputs Figure 9-13. Manage Team: Data Flow Diagram Figure 9-14. Control Resources: Inputs, Tools & Techniques, and Outputs Figure 9-15. Control Resources: Data Flow Diagram Figure 10-1. Project Communications Overview Plan Communications Management: Inputs, Tools & Techniques, Figure 10-2. and Outputs Figure 10-3. Plan Communications Management: Data Flow Diagram Figure 10-4. Communication Model for Cross-Cultural Communication Manage Communications: Inputs, Tools & Techniques, and Figure 10-5. Outputs Figure 10-6. Manage Communications: Data Flow Diagram Monitor Communications: Inputs, Tools & Techniques, and Figure 10-7. Outputs Figure 10-8. Monitor Communications: Data Flow Diagram Figure 11-1. Project Risk Management Overview Figure 11-2. Plan Risk Management: Inputs, Tools & Techniques, and Outputs Figure 11-3. Plan Risk Management: Data Flow Diagram Figure 11-4. Extract from Sample Risk Breakdown Structure (RBS) Figure 11-5. Example Probability and Impact Matrix with Scoring Scheme Figure 11-6. Identify Risks: Inputs, Tools & Techniques, and Outputs Figure 11-7. Identify Risks: Data Flow Diagram Perform Qualitative Risk Analysis: Inputs, Tools & Techniques, Figure 11-8. and Outputs Figure 11-9. Perform Qualitative Risk Analysis: Data Flow Diagram Example Bubble Chart Showing Detectability, Proximity, and Figure 11-10. Impact Value Perform Quantitative Risk Analysis: Inputs, Tools & Techniques, Figure 11-11. and Outputs Figure 11-12. Perform Quantitative Risk Analysis: Data Flow Diagram Figure 11-13. Example S-Curve from Quantitative Cost Risk Analysis Figure 11-14. Example Tornado Diagram Figure 11-15. Example Decision Tree Figure 11-16. Plan Risk Responses: Inputs, Tools & Techniques, and Outputs Figure 11-17. Plan Risk Responses: Data Flow Diagram Implement Risk Responses: Inputs, Tools & Techniques, and Figure 11-18. Outputs Figure 11-19. Implement Risk Responses: Data Flow Diagram Figure 11-20. Monitor Risks: Inputs, Tools & Techniques, and Outputs Figure 11-21. Monitor Risks: Data Flow Diagram Figure 12-1. Project Procurement Management Overview Plan Procurement Management: Inputs, Tools & Techniques, and Figure 12-2. Outputs Figure 12-3. Plan Procurement Management: Data Flow Diagram Figure 12-4. Conduct Procurements: Inputs, Tools & Techniques, and Outputs Figure 12-5. Conduct Procurements: Data Flow Diagram Figure 12-6. Control Procurements: Inputs, Tools & Techniques, and Outputs Figure 12-7. Control Procurements: Data Flow Diagram Figure 13-1. Project Stakeholder Management Overview Figure 13-2. Identify Stakeholders: Inputs, Tools & Techniques, and Outputs Figure 13-3. Identify Stakeholders: Data Flow Diagram Plan Stakeholder Engagement: Inputs, Tools & Techniques, and Figure 13-4. Outputs Figure 13-5. Plan Stakeholder Engagement: Data Flow Diagram Figure 13-6. Stakeholder Engagement Assessment Matrix Manage Stakeholder Engagement: Inputs, Tools & Techniques, Figure 13-7. and Outputs Figure 13-8. Manage Stakeholder Engagement: Data Flow Diagram Monitor Stakeholder Engagement: Inputs, Tools & Techniques, Figure 13-9. and Outputs Figure 13-10. Monitor Stakeholder Engagement: Data Flow Diagram Table 1-1. Examples of Factors that Lead to the Creation of a Project Table 1-2. Comparative Overview of Portfolios, Programs, and Projects Table 1-3. Description of PMBOK® Guide Key Components Project Management Process Group and Knowledge Area Table 1-4. Mapping Table 1-5. Project Business Documents Table 2-1. Influences of Organizational Structures on Projects Table 3-1. Team Management and Team Leadership Compared Table 4-1. Project Management Plan and Project Documents Table 5-1. Elements of the Project Charter and Project Scope Statement Table 7-1. Earned Value Calculations Summary Table Table 11-1. Example of Definitions for Probability and Impacts Table 12-1. Comparison of Procurement Documentation PART 2. The Standard For Project Management Example of Portfolio, Program, and Project Management Figure 1-1. Interfaces Figure 1-2. Generic Depiction of a Project Life Cycle Figure 1-3. Impact of Variables Over Time Figure 1-4. Examples of Project Stakeholders Figure 1-5. Example of Process Group Interactions Within a Project or Phase Figure 2-1. Project Boundaries Figure 2-2. Initiating Process Group Figure 2-3. Develop Project Charter: Inputs and Outputs Figure 2-4. Identify Stakeholders: Inputs and Outputs Figure 3-1. Planning Process Group Figure 3-2. Develop Project Management Plan: Inputs and Outputs Figure 3-3. Plan Scope Management: Inputs and Outputs Figure 3-4. Collect Requirements: Inputs and Outputs Figure 3-5. Define Scope: Inputs and Outputs Figure 3-6. Create WBS: Inputs and Outputs Figure 3-7. Plan Schedule Management: Inputs and Outputs Figure 3-8. Define Activities: Inputs and Outputs Figure 3-9. Sequence Activities: Inputs and Outputs Figure 3-10. Estimate Activity Durations: Inputs and Outputs Figure 3-11. Develop Schedule: Inputs and Outputs Figure 3-12. Plan Cost Management: Inputs and Outputs Figure 3-13. Estimate Costs: Inputs and Outputs Figure 3-14. Determine Budget: Inputs and Outputs Figure 3-15. Plan Quality Management: Inputs and Outputs Figure 3-16. Plan Resource Management: Inputs and Outputs Figure 3-17. Estimate Activity Resources: Inputs and Outputs Figure 3-18. Plan Communications Management: Inputs and Outputs Figure 3-19. Plan Risk Management: Inputs and Outputs Figure 3-20. Identify Risks: Inputs and Outputs Figure 3-21. Perform Qualitative Risk Analysis: Inputs and Outputs Figure 3-22. Perform Quantitative Risk Analysis: Inputs and Outputs Figure 3-23. Plan Risk Responses: Inputs and Outputs Figure 3-24. Plan Procurement Management: Inputs and Outputs Figure 3-25. Plan Stakeholder Engagement: Inputs and Outputs Figure 4-1. Executing Process Group Figure 4-2. Direct and Manage Project Work: Inputs and Outputs Figure 4-3. Manage Project Knowledge: Inputs and Outputs Figure 4-4. Manage Quality: Inputs and Outputs Figure 4-5. Acquire Resources: Inputs and Outputs Figure 4-6. Develop Team: Inputs and Outputs Figure 4-7. Manage Team: Inputs and Outputs Figure 4-8. Manage Communications: Inputs and Outputs Figure 4-9. Implement Risk Responses: Inputs and Outputs Figure 4-10. Conduct Procurements: Inputs and Outputs Figure 4-11. Manage Stakeholder Engagement: Inputs and Outputs Figure 5-1. Monitoring and Controlling Process Group Figure 5-2. Monitor and Control Project Work: Inputs and Outputs Figure 5-3. Perform Integrated Change Control: Inputs and Outputs Figure 5-4. Validate Scope: Inputs and Outputs Figure 5-5. Control Scope: Inputs and Outputs Figure 5-6. Control Schedule: Inputs and Outputs Figure 5-7. Control Costs: Inputs and Outputs Figure 5-8. Control Quality: Inputs and Outputs Figure 5-9. Control Resources: Inputs and Outputs Figure 5-10. Monitor Communications: Inputs and Outputs Figure 5-11. Monitor Risks: Inputs and Outputs Figure 5-12. Control Procurements: Inputs and Outputs Figure 5-13. Monitor Stakeholder Engagement: Inputs and Outputs Figure 6-1. Closing Process Group Figure 6-2. Close Project or Phase: Inputs and Outputs Project Management Process Group and Knowledge Area Table 1-1. Mapping Table 1-2. Project Management Plan and Project Documents PART 3. APPENDICES, GLOSSARY, AND INDEX Figure X3-1. The Continuum of Project Life Cycles Figure X3-2. Level of Effort for Process Groups across Iteration Cycles Figure X3-3. Relationship of Process Groups in Continuous Phases Table X1-1. Section 4 Changes Table X1-2. Section 6 Changes Table X1-3. Section 8 Changes Table X1-4. Section 9 Changes Table X1-5. Section 10 Changes Table X1-6. Section 11 Changes Table X1-7. Section 12 Changes Table X1-8. Section 13 Changes Table X6-1. Categorization and Index of Tools and Techniques Part 1 A Guide to the Project Management Body of Knowledge (PMBOK® GUIDE) The information contained in this part is not an American National Standard (ANS) and has not been processed in accordance with ANSI's requirements for an ANS. As such, the information in this part may contain material that has not been subjected to public review or a consensus process. In addition, it does not contain requirements necessary for conformance to an ANS standard. 1 INTRODUCTION 1.1 OVERVIEW AND PURPOSE OF THIS GUIDE Project management is not new. It has been in use for hundreds of years. Examples of project outcomes include: Pyramids of Giza, Olympic games, Great Wall of China, Taj Mahal, Publication of a children's book, Panama Canal, Development of commercial jet airplanes, Polio vaccine, Human beings landing on the moon, Commercial software applications, Portable devices to use the global positioning system (GPS), and Placement of the International Space Station into Earth's orbit. The outcomes of these projects were the result of leaders and managers applying project management practices, principles, processes, tools, and techniques to their work. The managers of these projects used a set of key skills and applied knowledge to satisfy their customers and other people involved in and affected by the project. By the mid-20th century, project managers began the work of seeking recognition for project management as a profession. One aspect of this work involved obtaining agreement on the content of the body of knowledge (BOK) called project management. This BOK became known as the Project Management Body of Knowledge (PMBOK). The Project Management Institute (PMI) produced a baseline of charts and glossaries for the PMBOK. Project managers soon realized that no single book could contain the entire PMBOK. Therefore, PMI developed and published A Guide to the Project Management Body of Knowledge (PMBOK® Guide). PMI defines the project management body of knowledge (PMBOK) as a term that describes the knowledge within the profession of project management. The project management body of knowledge includes proven traditional practices that are widely applied as well as innovative practices that are emerging in the profession. The body of knowledge (BOK) includes both published and unpublished materials. This body of knowledge is constantly evolving. This PMBOK® Guide identifies a subset of the project management body of knowledge that is generally recognized as good practice. Generally recognized means the knowledge and practices described are applicable to most projects most of the time, and there is consensus about their value and usefulness. Good practice means there is general agreement that the application of the knowledge, skills, tools, and techniques to project management processes can enhance the chance of success over many projects in delivering the expected business values and results. The project manager works with the project team and other stakeholders to determine and use the appropriate generally recognized good practices for each project. Determining the appropriate combination of processes, inputs, tools, techniques, outputs and life cycle phases to manage a project is referred to as “tailoring” the application of the knowledge described in this guide. This PMBOK® Guide is different from a methodology. A methodology is a system of practices, techniques, procedures, and rules used by those who work in a discipline. This PMBOK® Guide is a foundation upon which organizations can build methodologies, policies, procedures, rules, tools and techniques, and life cycle phases needed to practice project management. 1.1.1 THE STANDARD FOR PROJECT MANAGEMENT This guide is based on The Standard for Project Management. A standard is a document established by an authority, custom, or general consent as a model or example. As an American National Standards Institute (ANSI) standard, The Standard for Project Management was developed using a process based on the concepts of consensus, openness, due process, and balance. The Standard for Project Management is a foundational reference for PMI's project management professional development programs and the practice of project management. Because project management needs to be tailored to fit the needs of the project, the standard and the guide are both based on descriptive practices, rather than prescriptive practices. Therefore, the standard identifies the processes that are considered good practices on most projects, most of the time. The standard also identifies the inputs and outputs that are usually associated with those processes. The standard does not require that any particular process or practice be performed. The Standard for Project Management is included as Part II of A Guide to the Project Management Body of Knowledge (PMBOK® Guide). The PMBOK® Guide provides more detail about key concepts, emerging trends, considerations for tailoring the project management processes, and information on how tools and techniques are applied to projects. Project managers may use one or more methodologies to implement the project management processes outlined in the standard. The scope of this guide is limited to the discipline of project management, rather than the full spectrum of portfolios, programs, and projects. Portfolios and programs will be addressed only to the degree they interact with projects. PMI publishes two other standards that address the management of portfolios and programs: The Standard for Portfolio Management , and The Standard for Program Management. 1.1.2 COMMON VOCABULARY  A common vocabulary is an essential element of a professional discipline. The PMI Lexicon of Project Management Terms provides the foundational professional vocabulary that can be consistently used by organizations, portfolio, program, and project managers and other project stakeholders. The Lexicon will continue to evolve over time. The glossary to this guide includes the vocabulary in the Lexicon along with additional definitions. There may be other industry-specific terms used in projects that are defined by that industry's literature. 1.1.3 CODE OF ETHICS AND PROFESSIONAL CONDUCT PMI publishes the Code of Ethics and Professional Conduct to instill confidence in the project management profession and to help an individual in making wise decisions, particularly when faced with difficult situations where the individual may be asked to compromise his or her integrity or values. The values that the global project management community defined as most important were responsibility, respect, fairness, and honesty. The Code of Ethics and Professional Conduct affirms these four values as its foundation. The Code of Ethics and Professional Conduct includes both aspirational standards and mandatory standards. The aspirational standards describe the conduct that practitioners, who are also PMI members, certification holders, or volunteers, strive to uphold. Although adherence to the aspirational standards is not easily measured, conduct in accordance with these is an expectation for those who consider themselves to be professionals—it is not optional. The mandatory standards establish firm requirements and, in some cases, limit or prohibit practitioner behavior. Practitioners who are also PMI members, certification holders, or volunteers and who do not conduct themselves in accordance with these standards will be subject to disciplinary procedures before PMI's Ethics Review Committee. 1.2 FOUNDATIONAL ELEMENTS This section describes foundational elements necessary for working in and understanding the discipline of project management. 1.2.1 PROJECTS A project is a temporary endeavor undertaken to create a unique product, service, or result. Unique product, service, or result. Projects are undertaken to fulfill objectives by producing deliverables. An objective is defined as an outcome toward which work is to be directed, a strategic position to be attained, a purpose to be achieved, a result to be obtained, a product to be produced, or a service to be performed. A deliverable is defined as any unique and verifiable product, result, or capability to perform a service that is required to be produced to complete a process, phase, or project. Deliverables may be tangible or intangible. Fulfillment of project objectives may produce one or more of the following deliverables: A unique product that can be either a component of another item, an enhancement or correction to an item, or a new end item in itself (e.g., the correction of a defect in an end item); A unique service or a capability to perform a service (e.g., a business function that supports production or distribution);  A unique result, such as an outcome or document (e.g., a research project that develops knowledge that can be used to determine whether a trend exists or a new process will benefit society); and A unique combination of one or more products, services, or results (e.g., a software application, its associated documentation, and help desk services). Repetitive elements may be present in some project deliverables and activities. This repetition does not change the fundamental and unique characteristics of the project work. For example, office buildings can be constructed with the same or similar materials and by the same or different teams. However, each building project remains unique in key characteristics (e.g., location, design, environment, situation, people involved). Projects are undertaken at all organizational levels. A project can involve a single individual or a group. A project can involve a single organizational unit or multiple organizational units from multiple organizations. Examples of projects include but are not limited to: Developing a new pharmaceutical compound for market, Expanding a tour guide service, Merging two organizations, Improving a business process within an organization, Acquiring and installing a new computer hardware system for use in an organization, Exploring for oil in a region, Modifying a computer software program used in an organization, Conducting research to develop a new manufacturing process, and Constructing a building. Temporary endeavor. The temporary nature of projects indicates that a project has a definite beginning and end. Temporary does not necessarily mean a project has a short duration. The end of the project is reached when one or more of the following is true: The project's objectives have been achieved; The objectives will not or cannot be met; Funding is exhausted or no longer available for allocation to the project; The need for the project no longer exists (e.g., the customer no longer wants the project completed, a change in strategy or priority ends the project, the organizational management provides direction to end the project); The human or physical resources are no longer available; or The project is terminated for legal cause or convenience. Projects are temporary, but their deliverables may exist beyond the end of the project. Projects may produce deliverables of a social, economic, material, or environmental nature. For example, a project to build a national monument will create a deliverable expected to last for centuries. Projects drive change. Projects drive change in organizations. From a business perspective, a project is aimed at moving an organization from one state to another state in order to achieve a  specific objective (see Figure 1-1). Before the project begins, the organization is commonly referred to as being in the current state. The desired result of the change driven by the project is described as the future state. For some projects, this may involve creating a transition state where multiple steps are made along a continuum to achieve the future state. The successful completion of a project results in the organization moving to the future state and achieving the specific objective. For more information on project management and change, see Managing Change in Organizations: A Practice Guide. Projects enable business value creation. PMI defines business value as the net quantifiable benefit derived from a business endeavor. The benefit may be tangible, intangible, or both. In business analysis, business value is considered the return, in the form of elements such as time, money, goods, or intangibles in return for something exchanged (see Business Analysis for Practitioners: A Practice Guide, p. 185 ). Business value in projects refers to the benefit that the results of a specific project provide to its stakeholders. The benefit from projects may be tangible, intangible, or both. Examples of tangible elements include: Monetary assets, Stockholder equity, Utility, Fixtures, Tools, and Market share. Examples of intangible elements include: Goodwill, Brand recognition, Public benefit,  Trademarks, Strategic alignment, and Reputation. Project Initiation Context. Organizational leaders initiate projects in response to factors acting upon their organizations. There are four fundamental categories for these factors, which illustrate the context of a project (see Figure 1-2): Meet regulatory, legal, or social requirements; Satisfy stakeholder requests or needs; Implement or change business or technological strategies; and Create, improve, or fix products, processes, or services. These factors influence an organization's ongoing operations and business strategies. Leaders respond to these factors in order to keep the organization viable. Projects provide the means for organizations to successfully make the changes necessary to deal with these factors. These factors ultimately should link to the strategic objectives of the organization and the business value of each project. 1.2.2 THE IMPORTANCE OF PROJECT MANAGEMENT Project management is the application of knowledge, skills, tools, and techniques to project activities to meet the project requirements. Project management is accomplished through the appropriate application and integration of the project management processes identified for the project. Project management enables organizations to execute projects effectively and efficiently. Effective project management helps individuals, groups, and public and private organizations to: Meet business objectives; Satisfy stakeholder expectations; Be more predictable; Increase chances of success; Deliver the right products at the right time; Resolve problems and issues; Respond to risks in a timely manner; Optimize the use of organizational resources; Identify, recover, or terminate failing projects; Manage constraints (e.g., scope, quality, schedule, costs, resources);  Balance the influence of constraints on the project (e.g., increased scope may increase cost or schedule); and Manage change in a better manner. Poorly managed projects or the absence of project management may result in: Missed deadlines, Cost overruns, Poor quality, Rework, Uncontrolled expansion of the project, Loss of reputation for the organization, Unsatisfied stakeholders, and Failure in achieving the objectives for which the project was undertaken. Projects are a key way to create value and benefits in organizations. In today's business environment, organizational leaders need to be able to manage with tighter budgets, shorter timelines, scarcity of resources, and rapidly changing technology. The business environment is dynamic with an accelerating rate of change. To remain competitive in the world economy, companies are embracing project management to consistently deliver business value. Effective and efficient project management should be considered a strategic competency within organizations. It enables organizations to: Tie project results to business goals, Compete more effectively in their markets, Sustain the organization, and Respond to the impact of business environment changes on projects by appropriately adjusting project management plans (see Section 4.2). 1.2.3 RELATIONSHIP OF PROJECT, PROGRAM, PORTFOLIO, AND OPERATIONS MANAGEMENT 1.2.3.1 OVERVIEW Using project management processes, tools, and techniques puts in place a sound foundation for organizations to achieve their goals and objectives. A project may be managed in three separate scenarios: as a stand-alone project (outside of a portfolio or program), within a program, or within a portfolio. Project managers interact with portfolio and program managers when a project is within a program or portfolio. For example, multiple projects may be needed to accomplish a set of goals and objectives for an organization. In those situations, projects may be grouped together into a program. A program is defined as a group of related projects, subsidiary programs, and program activities managed in a coordinated manner to obtain benefits not available from managing them individually. Programs are not large projects. A very large project may be referred to as a megaproject. As a guideline, megaprojects cost US$1billion or more, affect 1 million or more people, and run for years.  Some organizations may employ the use of a project portfolio to effectively manage multiple programs and projects that are underway at any given time. A portfolio is defined as projects, programs, subsidiary portfolios, and operations managed as a group to achieve strategic objectives. Figure 1-3 illustrates an example of how portfolios, programs, projects, and operations are related in a specific situation. Program management and portfolio management differ from project management in their life cycles, activities, objectives, focus, and benefits. However, portfolios, programs, projects, and operations often engage with the same stakeholders and may need to use the same resources (see Figure 1-3), which may result in a conflict in the organization. This type of a situation increases the need for coordination within the organization through the use of portfolio, program, and project management to achieve a workable balance in the organization. Figure 1-3 illustrates a sample portfolio structure indicating relationships between the programs, projects, shared resources, and stakeholders. The portfolio components are grouped together in order to facilitate the effective governance and management of the work that helps to achieve organizational strategies and priorities. Organizational and portfolio planning impact the components by means of prioritization based on risk, funding, and other considerations. The portfolio view allows organizations to see how the strategic goals are reflected in the portfolio. This portfolio view also enables the implementation and coordination of appropriate portfolio, program, and project governance. This coordinated governance allows authorized allocation of human, financial, and physical resources based on expected performance and benefits. Looking at project, program, and portfolio management from an organizational perspective: Program and project management focus on doing programs and projects the “right” way; and Portfolio management focuses on doing the “right” programs and projects. Table 1-2 gives a comparative overview of portfolios, programs, and projects. 1.2.3.2 PROGRAM MANAGEMENT Program management is defined as the application of knowledge, skills, and principles to a program to achieve the program objectives and to obtain benefits and control not available by managing program components individually. A program component refers to projects and other programs within a program. Project management focuses on interdependencies within a project to determine the optimal approach for managing the project. Program management focuses on the interdependencies between projects and between projects and the program level to determine the optimal approach for managing them. Actions related to these program and project-level interdependencies may include: Aligning with the organizational or strategic direction that affects program and project goals and objectives; Allocating the program scope into program components; Managing interdependencies among the components of the program to best serve the program; Managing program risks that may impact multiple projects in the program; Resolving constraints and conflicts that affect multiple projects within the program; Resolving issues between component projects and the program level; Managing change requests within a shared governance framework; Allocating budgets across multiple projects within the program; and Assuring benefits realization from the program and component projects. An example of a program is a new communications satellite system with projects for the design and construction of the satellite and the ground stations, the launch of the satellite, and the integration of the system. For more information on program management, see The Standard for Program Management. 1.2.3.3 PORTFOLIO MANAGEMENT A portfolio is defined as projects, programs, subsidiary portfolios, and operations managed as a group to achieve strategic objectives. Portfolio management is defined as the centralized management of one or more portfolios to achieve strategic objectives. The programs or projects of the portfolio may not necessarily be interdependent or directly related. The aim of portfolio management is to: Guide organizational investment decisions. Select the optimal mix of programs and projects to meet strategic objectives. Provide decision-making transparency. Prioritize team and physical resource allocation. Increase the likelihood of realizing the desired return on investment. Centralize the management of the aggregate risk profile of all components. Portfolio management also confirms that the portfolio is consistent with and aligned with organizational strategies. Maximizing the value of the portfolio requires careful examination of the components that comprise the portfolio. Components are prioritized so that those contributing the most to the organization's strategic objectives have the required financial, team, and physical resources. For example, an infrastructure organization that has the strategic objective of maximizing the return on its investments may put together a portfolio that includes a mix of projects in oil and gas, power, water, roads, rail, and airports. From this mix, the organization may choose to manage related projects as one portfolio. All of the power projects may be grouped together as a power portfolio. Similarly, all of the water projects may be grouped together as a water portfolio. However, when the organization has projects in designing and constructing a power plant and then operates the power plant to generate energy, those related projects can be grouped in one program. Thus, the power program and similar water program become integral components of the portfolio of the infrastructure organization. For more information on portfolio management, see The Standard for Portfolio Management. 1.2.3.4 OPERATIONS MANAGEMENT Operations management is an area that is outside the scope of formal project management as described in this guide. Operations management is concerned with the ongoing production of goods and/or services. It ensures that business operations continue efficiently by using the optimal resources needed to meet customer demands. It is concerned with managing processes that transform inputs (e.g., materials, components, energy, and labor) into outputs (e.g., products, goods, and/or services). 1.2.3.5 OPERATIONS AND PROJECT MANAGEMENT  Changes in business or organizational operations may be the focus of a project—especially when there are substantial changes to business operations as a result of a new product or service delivery. Ongoing operations are outside of the scope of a project; however, there are intersecting points where the two areas cross. Projects can intersect with operations at various points during the product life cycle, such as; When developing a new product, upgrading a product, or expanding outputs; While improving operations or the product development process; At the end of the product life cycle; and At each closeout phase. At each point, deliverables and knowledge are transferred between the project and operations for implementation of the delivered work. This implementation occurs through a transfer of project resources or knowledge to operations or through a transfer of operational resources to the project. 1.2.3.6 ORGANIZATIONAL PROJECT MANAGEMENT (OPM) AND STRATEGIES Portfolios, programs, and projects are aligned with or driven by organizational strategies and differ in the way each contributes to the achievement of strategic goals: Portfolio management aligns portfolios with organizational strategies by selecting the right programs or projects, prioritizing the work, and providing the needed resources. Program management harmonizes its program components and controls interdependencies in order to realize specified benefits. Project management enables the achievement of organizational goals and objectives. Within portfolios or programs, projects are a means of achieving organizational goals and objectives. This is often accomplished in the context of a strategic plan that is the primary factor guiding investments in projects. Alignment with the organization's strategic business goals can be achieved through the systematic management of portfolios, programs, and projects through the application of organizational project management (OPM). OPM is defined as a framework in which portfolio, program, and project management are integrated with organizational enablers in order to achieve strategic objectives. The purpose of OPM is to ensure that the organization undertakes the right projects and allocates critical resources appropriately. OPM also helps to ensure that all levels in the organization understand the strategic vision, the initiatives that support the vision, the objectives, and the deliverables. Figure 1-4 shows the organizational environment where strategy, portfolio, programs, projects, and operations interact. For more information on OPM, refer to Implementing Organizational Project Management: A Practice Guide. 1.2.4 COMPONENTS OF THE GUIDE Projects comprise several key components that, when effectively managed, result in their successful completion. This guide identifies and explains these components. The various components interrelate to one another during the management of a project. The key components are described briefly in Table 1-3. These components are more fully explained in the sections that follow the table. Table 1-3. Description of PMBOK® Guide Key Components PMBOK® Guide Key Component Brief Description Project life cycle (Section 1.2.4.1) The series of phases that a project passes through from its start to its completion. A collection of logically related project activities that culminates in the completion Project phase (Section 1.2.4.2) of one or more deliverables. A review at the end of a phase in which a decision is made to continue to the Phase gate (Section 1.2.4.3) next phase, to continue with modification, or to end a program or project. A systematic series of activities directed toward causing an end result where one Project management processes (Section 1.2.4.4) or more inputs will be acted upon to create one or more outputs. A logical grouping of project management inputs, tools and techniques, and Project Management Process Group (Section outputs. The Project Management Process Groups include Initiating, Planning, 1.2.4.5) Executing, Monitoring and Controlling, and Closing. Project Management Process Groups are not project phases. An identified area of project management defined by its knowledge requirements Project Management Knowledge Area (Section and described in terms of its component processes, practices, inputs, outputs, 1.2.4.6) tools, and techniques. 1.2.4.1 PROJECT AND DEVELOPMENT LIFE CYCLES A project life cycle is the series of phases that a project passes through from its start to its completion. It provides the basic framework for managing the project. This basic framework applies regardless of the specific project work involved. The phases may be sequential, iterative, or overlapping. All projects can be mapped to the generic life cycle shown in Figure 1-5. Project life cycles can be predictive or adaptive. Within a project life cycle, there are generally one or more phases that are associated with the development of the product, service, or result. These are called a development life cycle. Development life cycles can be predictive, iterative, incremental, adaptive, or a hybrid model: In a predictive life cycle, the project scope, time, and cost are determined in the early phases of the life cycle. Any changes to the scope are carefully managed. Predictive life cycles may also be referred to as waterfall life cycles. In an iterative life cycle, the project scope is generally determined early in the project life cycle, but time and cost estimates are routinely modified as the project team's understanding of the product increases. Iterations develop the product through a series of repeated cycles, while increments successively add to the functionality of the product. In an incremental life cycle, the deliverable is produced through a series of iterations that successively add functionality within a predetermined time frame. The deliverable contains the necessary and sufficient capability to be considered complete only after the final iteration. Adaptive life cycles are agile, iterative, or incremental. The detailed scope is defined and  approved before the start of an iteration. Adaptive life cycles are also referred to as agile or change-driven life cycles. See Appendix X3. A hybrid life cycle is a combination of a predictive and an adaptive life cycle. Those elements of the project that are well known or have fixed requirements follow a predictive development life cycle, and those elements that are still evolving follow an adaptive development life cycle. It is up to the project management team to determine the best life cycle for each project. The project life cycle needs to be flexible enough to deal with the variety of factors included in the project. Life cycle flexibility may be accomplished by: Identifying the process or processes needed to be performed in each phase, Performing the process or processes identified in the appropriate phase, Adjusting the various attributes of a phase (e.g., name, duration, exit criteria, and entrance criteria). Project life cycles are independent of product life cycles, which may be produced by a project. A product life cycle is the series of phases that represent the evolution of a product, from concept through delivery, growth, maturity, and to retirement. 1.2.4.2 PROJECT PHASE A project phase is a collection of logically related project activities that culminates in the completion of one or more deliverables. The phases in a life cycle can be described by a variety of attributes. Attributes may be measurable and unique to a specific phase. Attributes may include but are not limited to: Name (e.g., Phase A, Phase B, Phase 1, Phase 2, proposal phase), Number (e.g., three phases in the project, five phases in the project), Duration (e.g., 1 week, 1 month, 1 quarter), Resource requirements (e.g., people, buildings, equipment), Entrance criteria for a project to move into that phase (e.g., specified approvals documented, specified documents completed), and Exit criteria for a project to complete a phase (e.g., documented approvals, completed documents, completed deliverables). Projects may be separated into distinct phases or subcomponents. These phases or subcomponents are generally given names that indicate the type of work done in that phase. Examples of phase names include but are not limited to: Concept development, Feasibility study, Customer requirements, Solution development, Design, Prototype, Build,  Test, Transition, Commissioning, Milestone review, and Lessons learned. The project phases may be established based on various factors including, but not limited to: Management needs; Nature of the project; Unique characteristics of the organization, industry, or technology; Project elements including, but not limited to, technology, engineering, business, process, or legal; and Decision points (e.g., funding, project go/no-go, and milestone review). Using multiple phases may provide better insight to managing the project. It also provides an opportunity to assess the project performance and take necessary corrective or preventive actions in subsequent phases. A key component used with project phases is the phase review (see Section 1.2.4.3). 1.2.4.3 PHASE GATE A phase gate, is held at the end of a phase. The project's performance and progress are compared to project and business documents including but not limited to: Project business case (see Section 1.2.6.1), Project charter (see Section 4.1), Project management plan (see Section 4.2), and Benefits management plan (see Section 1.2.6.2). A decision (e.g., go/no-go decision) is made as a result of this comparison to: Continue to the next phase, Continue to the next phase with modification, End the project, Remain in the phase, or Repeat the phase or elements of it. Depending on the organization, industry, or type of work, phase gates may be referred to by other terms such as, phase review, stage gate, kill point, and phase entrance or phase exit. Organizations may use these reviews to examine other pertinent items which are beyond the scope of this guide, such as product- related documents or models. 1.2.4.4 PROJECT MANAGEMENT PROCESSES The project life cycle is managed by executing a series of project management activities known as project management processes. Every project management process produces one or more outputs from one or more inputs by using appropriate project management tools and techniques. The output can be a deliverable or an outcome. Outcomes are an end result of a process. Project management processes apply globally across industries. Project management processes are logically linked by the outputs they produce. Processes may contain overlapping activities that occur throughout the project. The output of one process generally results in either: An input to another process, or A deliverable of the project or project phase. Figure 1-6 shows an example of how inputs, tools and techniques, and outputs relate to each other within a process, and with other processes. The number of process iterations and interactions between processes varies based on the needs of the project. Processes generally fall into one of three categories: Processes used once or at predefined points in the project. The processes Develop Project Charter and Close Project or Phase are examples. Processes that are performed periodically as needed. The process Acquire Resources is performed as resources are needed. The process Conduct Procurements is performed prior to needing the procured item. Processes that are performed continuously throughout the project. The process Define Activities may occur throughout the project life cycle, especially if the project uses rolling wave planning or an adaptive development approach. Many of the monitoring and control processes are ongoing from the start of the project, until it is closed out. Project management is accomplished through the appropriate application and integration of logically grouped project management processes. While there are different ways of grouping processes, the PMBOK® Guide groups processes into five categories called Process Groups. 1.2.4.5 PROJECT MANAGEMENT PROCESS GROUPS A Project Management Process Group is a logical grouping of project management processes to achieve specific project objectives. Process Groups are independent of project phases. Project management processes are grouped into the following five Project Management Process Groups: Initiating Process Group. Those processes performed to define a new project or a new phase of an existing project by obtaining authorization to start the project or phase. Planning Process Group. Those processes required to establish the scope of the project, refine the objectives, and define the course of action required to attain the objectives that the project was undertaken to achieve. Executing Process Group. Those processes performed to complete the work defined in the  project management plan to satisfy the project requirements. Monitoring and Controlling Process Group. Those processes required to track, review, and regulate the progress and performance of the project; identify any areas in which changes to the plan are required; and initiate the corresponding changes. Closing Process Group. Those processes performed to formally complete or close the project, phase, or contract. Process flow diagrams are used throughout this guide. The project management processes are linked by specific inputs and outputs where the result or outcome of one process may become the input to another process that is not necessarily in the same Process Group. Note that Process Groups are not the same as project phases (see Section 1.2.4.2). 1.2.4.6 PROJECT MANAGEMENT KNOWLEDGE AREAS In addition to Process Groups, processes are also categorized by Knowledge Areas. A Knowledge Area is an identified area of project management defined by its knowledge requirements and described in terms of its component processes, practices, inputs, outputs, tools, and techniques. Although the Knowledge Areas are interrelated, they are defined separately from the project management perspective. The ten Knowledge Areas identified in this guide are used in most projects most of the time. The ten Knowledge Areas described in this guide are: Project Integration Management. Includes the processes and activities to identify, define, combine, unify, and coordinate the various processes and project management activities within the Project Management Process Groups. Project Scope Management. Includes the processes required to ensure the project includes all the work required, and only the work required, to complete the project successfully. Project Schedule Management. Includes the processes required to manage the timely completion of the project. Project Cost Management. Includes the processes involved in planning, estimating, budgeting, financing, funding, managing, and controlling costs so the project can be completed within the approved budget. Project Quality Management. Includes the processes for incorporating the organization's quality policy regarding planning, managing, and controlling project and product quality requirements, in order to meet stakeholders’ expectations. Project Resource Management. Includes the processes to identify, acquire, and manage the resources needed for the successful completion of the project. Project Communications Management. Includes the processes required to ensure timely and appropriate planning, collection, creation, distribution, storage, retrieval, management, control, monitoring, and ultimate disposition of project information. Project Risk Management. Includes the processes of conducting risk management planning, identification, analysis, response planning, response implementation, and monitoring risk on a project. Project Procurement Management. Includes the processes necessary to purchase or acquire products, services, or results needed from outside the project team. Project Stakeholder Management. Includes the processes required to identify the people,  groups, or organizations that could impact or be impacted by the project, to analyze stakeholder expectations and their impact on the project, and to develop appropriate management strategies for effectively engaging stakeholders in project decisions and execution. The needs of a specific project may require one or more additional Knowledge Areas, for example, construction may require financial management or safety and health management. Table 1-4 maps the Project Management Process Groups and Knowledge Areas. Sections 4 through 13 provide more detail about each Knowledge Area. This table is an overview of the basic processes described in Sections 4 through 13. 1.2.4.7 PROJECT MANAGEMENT DATA AND INFORMATION Throughout the life cycle of a project, a significant amount of data is collected, analyzed, and transformed. Project data are collected as a result of various processes and are shared within the project team. The collected data are analyzed in context, aggregated, and transformed to become project information during various processes. Information is communicated verbally or stored and distributed in various formats as reports. See Section 4.3 for more detail on this topic. Project data are regularly collected and analyzed throughout the project life cycle. The following definitions identify key terminology regarding project data and information: Work performance data. The raw observations and measurements identified during activities performed to carry out the project work. Examples include reported percent of work physically completed, quality and technical performance measures, start and finish dates of schedule activities, number of change requests, number of defects, actual costs, actual durations, etc.  Project data are usually recorded in a Project Management Information System (PMIS) (see Section 4.3.2.2) and in project documents. Work performance information. The performance data collected from various controlling processes, analyzed in context and integrated based on relationships across areas. Examples of performance information are status of deliverables, implementation status for change requests, and forecast estimates to complete. Work performance reports. The physical or electronic representation of work performance information compiled in project documents, which is intended to generate decisions or raise issues, actions, or awareness. Examples include status reports, memos, justifications, information notes, electronic dashboards, recommendations, and updates. Figure 1-7 shows the flow of project information across the various processes used in managing the project. 1.2.5 TAILORING Usually, project managers apply a project management methodology to their work. A methodology is a system of practices, techniques, procedures, and rules used by those who work in a discipline. This definition makes it clear that this guide itself is not a methodology. This guide and The Standard for Project Management are recommended references for tailoring, because these standard documents identify the subset of the project management body of knowledge that is generally recognized as good practice. “Good practice” does not mean that the knowledge described should always be applied uniformly to all projects. Specific methodology recommendations are outside the scope of this guide. Project management methodologies may be: Developed by experts within the organization, Purchased from vendors, Obtained from professional associations, or Acquired from government agencies. The appropriate project management processes, inputs, tools, techniques, outputs, and life cycle phases should be selected to manage a project. This selection activity is known as tailoring project management to the project. The project manager collaborates with the project team, sponsor, organizational management, or some combination thereof, in the tailoring. In some cases, the organization may require specific project management methodologies be used. Tailoring is necessary because each project is unique; not every process, tool, technique, input, or output identified in the PMBOK® Guide is required on every project. Tailoring should address the competing constraints of scope, schedule, cost, resources, quality, and risk. The importance of each constraint is different for each project, and the project manager tailors the approach for managing these constraints based on the project environment, organizational culture, stakeholder needs, and other variables. In tailoring project management, the project manager should also consider the varying levels of governance that may be required and within which the project will operate, as well as considering the culture of the organization. In addition, consideration of whether the customer of the project is internal or external to the organization may affect project management tailoring decisions. Sound project management methodologies take into account the unique nature of projects and allow tailoring, to some extent, by the project manager. However, the tailoring that is included in the methodology may still require additional tailoring for a given project. 1.2.6 PROJECT MANAGEMENT BUSINESS DOCUMENTS The project manager needs to ensure that the project management approach captures the intent of business documents. These documents are defined in Table 1-5. These two documents are interdependent and iteratively developed and maintained throughout the life cycle of the project. Table 1-5. Project Business Documents Project Business Documents Definition A documented economic feasibility study used to establish the validity of the Project business case benefits of a selected component lacking sufficient definition and that is used as a basis for the authorization of further project management activities. The documented explanation defining the processes for creating, maximizing, and Project benefits management plan sustaining the benefits provided by a project. The project sponsor is generally accountable for the development and maintenance of the project business case document. The project manager is responsible for providing recommendations and oversight to keep the project business case, project management plan, project charter, and project benefits management plan success measures in alignment with one another and with the goals and objectives of the organization. Project managers should appropriately tailor the noted project management documents for their projects. In some organizations, the business case and benefits management plan are maintained at the program level. Project managers should work with the appropriate program managers to ensure the project management documents are aligned with the program documents. Figure 1-8 illustrates the interrelationship of these critical project management business documents and the needs assessment. Figure 1-8 shows an approximation of the life cycle of these various documents against the project life cycle. 1.2.6.1 PROJECT BUSINESS CASE The project business case is a documented economic feasibility study used to establish the validity of the benefits of a selected component lacking sufficient definition and that is used as a basis for the authorization of further project management activities. The business case lists the objectives and reasons for project initiation. It helps measure the project success at the end of the project against the project objectives. The business case is a project business document that is used throughout the project life cycle. The business case may be used before the project initiation and may result in a go/no-go decision for the project. A needs assessment often precedes the business case. The needs assessment involves understanding business goals and objectives, issues, and opportunities and recommending proposals to address them. The results of the needs assessment may be summarized in the business case document. The process of defining the business need, analyzing the situation, making recommendations, and defining evaluation criteria is applicable to any organization's projects. A business case may include but is not limited to documenting the following: Business needs:  Determination of what is prompting the need for action; Situational statement documenting the business problem or opportunity to be addressed including the value to be delivered to the organization; Identification of stakeholders affected; and Identification of the scope. Analysis of the situation: Identification of organizational strategies, goals, and objectives; Identification of root cause(s) of the problem or main contributors of an opportunity; Gap analysis of capabilities needed for the project versus existing capabilities of the organization; Identification of known risks; Identification of critical success factors; Identification of decision criteria by which the various courses of action may be assessed; Examples of criteria categories used for analysis of a situation are: Required. This is a criterion that is “required” to be fulfilled to address the problem or opportunity. Desired. This is a criterion that is “desired” to be fulfilled to address the problem or opportunity. Optional. This is a criterion that is not essential. Fulfillment of this criterion may become a differentiator between alternative courses of action. Identification of a set of options to be considered for addressing the business problem or opportunity. Options are alternative courses of action that may be taken by the organization. Options may also be described as business scenarios. For example, a business case could present the following three options: Do nothing. This is also referred to as the “business as usual” option. Selection of this option results in the project not being authorized. Do the minimum work possible to address the problem or opportunity. The minimum may be established by identifying the set of documented criteria that are key in addressing the problem or opportunity. Do more than the minimum work possible to address the problem or opportunity. This option meets the minimum set of criteria and some or all of the other documented criteria. There may be more than one of these options documented in the business case. Recommendation: A statement of the recommended option to pursue in the project; Items to include in the statement may include but are not limited to: Analysis results for the potential option; Constraints, assumptions, risks, and dependencies for the potential options; and Success measures (see Section 1.2.6.4).  An implementation approach that may include but is not limited to: Milestones, Dependencies, and Roles and responsibilities. Evaluation: Statement describing the plan for measuring benefits the project will deliver. This should include any ongoing operational aspects of the recommended option beyond initial implementation. The business case document provides the basis to measure success and progress throughout the project life cycle by comparing the results with the objectives and the identified success criteria. See Business Analysis for Practitioners: A Practice Guide. 1.2.6.2 PROJECT BENEFITS MANAGEMENT PLAN The project benefits management plan is the document that describes how and when the benefits of the project will be delivered, and describes the mechanisms that should be in place to measure those benefits. A project benefit is defined as an outcome of actions, behaviors, products, services, or results that provide value to the sponsoring organization as well as to the project's intended beneficiaries. Development of the benefits management plan begins early in the project life cycle with the definition of the target benefits to be realized. The benefits management plan describes key elements of the benefits and may include but is not limited to documenting the following: Target benefits (e.g., the expected tangible and intangible value to be gained by the implementation of the project; financial value is expressed as net present value); Strategic alignment (e.g., how well the project benefits align to the business strategies of the organization); Timeframe for realizing benefits (e.g., benefits by phase, short-term, long-term, and ongoing); Benefits owner (e.g., the accountable person to monitor, record, and report realized benefits throughout the timeframe established in the plan); Metrics (e.g., the measures to be used to show benefits realized, direct measures, and indirect measures); Assumptions (e.g., factors expected to be in place or to be in evidence); and Risks (e.g., risks for realization of benefits). Developing the benefits management plan makes use of the data and information documented in the business case and needs assessment. For example, the cost-benefit analyses recorded in the documents illustrate the estimate of costs compared to the value of the benefits realized by the project. The benefits management plan and the project management plan include a description of how the business value resulting from the project becomes part of the organization's ongoing operations, including the metrics to be used. The metrics provide verification of the business value and validation of the project's success. Development and maintenance of the project benefits management plan is an iterative activity. This document complements the business case, project charter, and project management plan. The project manager works with the sponsor to ensure that the project charter, project management plan, and the benefits management plan remain in alignment throughout the life cycle of the project. See Business Analysis for Practitioners: A Practice Guide , The Standard for Program Management , and The Standard for Portfolio Management. 1.2.6.3 PROJECT CHARTER AND PROJECT MANAGEMENT PLAN The project charter is defined as a document issued by the project sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities. The project management plan is defined as the document that describes how the project will be executed, monitored, and controlled. See Section 4 on Project Integration Management for more information on the project charter and the project management plan. 1.2.6.4 PROJECT SUCCESS MEASURES One of the most common challenges in project management is determining whether or not a project is successful. Traditionally, the project management metrics of time, cost, scope, and quality have been the most important factors in defining the success of a project. More recently, practitioners and scholars have