MANAGEMENT

Recommendations

Info

1 - INTRODUCTION need to understand the risks and impacts that poor requirements management is having on their projects and programs and need to receive guidance to address these deficiencies. This document will also be valuable to anyone who is responsible for performing requirements work, or for project stakeholders who interact with practitioners performing requirements activities. It was also developed to help those interested in improving their requirements-related competencies and for those interested in improving their knowledge of requirements processes and the application of this work on programs and projects. 1 1.4 Summary The principles of requirements development and management as described in this practice guide should be appropriately applied based on the specifics of a project and the organizational environment. Effective requirements practices provide organizational benefits when they are consistent with organizational strategy and objectives by implementing good practice principles aligned with strong organizational commitment. ©2016 Project Management Institute. Requirements Management: A Practice Guide 3
Page 1 and 2: REQUIREMENTS MANAGEMENT A PRACTICE
Page 3 and 4: Library of Congress Cataloging-in-P
Page 5 and 6: TABLE OF CONTENTS 3.3.4 Create Bene
Page 7 and 8: TABLE OF CONTENTS 6.3 Requirements
Page 9 and 10: PREFACE Requirements Management: A
Page 12 and 13: 1 - INTRODUCTION 1 1 INTRODUCTION 1
Page 16 and 17: 2 - REQUIREMENTS MANAGEMENT OVERVIE
Page 22: 2 - REQUIREMENTS MANAGEMENT OVERVIE
Page 25 and 26: 3 - NEEDS ASSESSMENT needs assessme
Page 27 and 28: 3 - NEEDS ASSESSMENT 3.4 Needs Asse
Page 30 and 31: 4 - REQUIREMENTS MANAGEMENT PLANNIN
Page 32 and 33: 4 - REQUIREMENTS MANAGEMENT PLANNIN
Page 34: 4 - REQUIREMENTS MANAGEMENT PLANNIN
Page 37 and 38: 5 - REQUIREMENTS ELICITATION 5.1.2
Page 39 and 40: 5 - REQUIREMENTS ELICITATION • Tr
Page 41 and 42: 5 - REQUIREMENTS ELICITATION other
Page 44 and 45: 6 - REQUIREMENTS ANALYSIS 6 REQUIRE
Page 46 and 47: 6 - REQUIREMENTS ANALYSIS 6.2.2.2 S
Page 48 and 49: 6 - REQUIREMENTS ANALYSIS • Estim
Page 50 and 51: 6 - REQUIREMENTS ANALYSIS of the sy
Page 52: 6 - REQUIREMENTS ANALYSIS • Data
Page 55 and 56: 7 - REQUIREMENTS MONITORING AND CON
Page 61 and 62: 8 - SOLUTION EVALUATION 8.2.1 Plan
Page 64 and 65:
9 - PROJECT OR PHASE CLOSURE 9 PROJ
Page 66 and 67:
9 - PROJECT OR PHASE CLOSURE a prog
Page 68 and 69:
APPENDIX X1 - CONTRIBUTORS AND REVI
Page 70 and 71:
APPENDIX X2 - SUGGESTED ADDITIONAL
Page 72 and 73:
APPENDIX X3 - REQUIREMENTS MANAGEME
Page 74:
REFERENCES REFERENCES [1] Project M
Page 77 and 78:
GLOSSARY Business Analysis Planning
Page 79 and 80:
GLOSSARY Estimate. A quantitative a
Page 81 and 82:
GLOSSARY Open-Ended Question. A que
Page 83 and 84:
GLOSSARY Report Table. A business a
Page 85 and 86:
GLOSSARY Stakeholder Requirement. A
Page 88 and 89:
INDEX INDEX Acceptance, customer, i
Page 90 and 91:
INDEX Job shadowing, 31 Judgment, e
Page 92 and 93:
INDEX Requirements attributes, 34,
show all

MANAGEMENT

Create successful ePaper yourself

Delete template?

Save as template?