MANAGEMENT

Recommendations

Info

7 - REQUIREMENTS MONITORING AND CONTROLLING 7 REQUIREMENTS MONITORING AND CONTROLLING The requirements monitoring and controlling domain iteratively monitors the status of requirements and manages the requirements baseline over the project life cycle. In the context of the requirements process, activities include monitoring and controlling so changes to the requirements themselves are approved and managed. It should be noted that the process and related activities involved in the development and management of requirements are distinct from the project management life cycle. 7 The requirements traceability matrix and associated attributes created during elicitation and analysis are applied in requirements monitoring to help control the product and project scope. Traceability is updated as changes are approved. Approved requirements are baselined and tracked, to include linkages among parent and child requirements. As new requirements are identified, they are assessed for impacts to the project and product and presented to stakeholders for approval. Throughout monitoring and controlling, the status of requirements is communicated using the communication methods defined and approved within the communications management plans. This section will describe requirements monitoring and controlling success factors, activities, and techniques. Requirements instability is a leading cause of scope creep, and the requirements monitoring and controlling activities ensure that requested changes to requirements are processed through the Perform Integrated Change Control process as described in Section 4.5 of the PMBOK ® Guide – Fifth Edition and in greater detail in the Practice Standard for Project Configuration Management [6]. In an adaptive life cycle, scope is controlled during monitoring and controlling by managing the backlog. The backlog is reviewed and revised for each iteration, thereby allowing more opportunity for new requirements to be addressed. Once the scope of an iteration is decided upon, changes are managed and controlled accordingly. Traceability provides the ability to track product requirements from their origin to the activities and deliverables that satisfy them. Traceability is “bidirectional” or “forward and backward.” Not all projects require the same amount of traceability documentation, so the specific deliverables that are traceable for the project are determined during requirements management planning. Generally, the more complex projects require more traceability. A project in a heavily regulated industry or one with numerous components, interfaces, risks, and stakeholders requires more detailed traceability than a project without those characteristics. 7.1 Requirements Monitoring and Controlling Success Factors From the start, the project management plan should include the activities required to monitor and control project baselines. The application of the overall project baseline monitoring and controlling processes to the requirements baseline should be defined in the requirements management plan, as described in Sections 4 and 7.2. ©2016 Project Management Institute. Requirements Management: A Practice Guide 43
7 - REQUIREMENTS MONITORING AND CONTROLLING Key requirements should be identified and marked as such, and monitored continuously. These requirements, sometimes referred to as key performance indicators, are those requirements for which the inability to meet a threshold value puts the project at risk of failing to meet the business need of the organization. 7.2 Requirements Monitoring and Controlling Activities After creating the traceability matrix during elicitation and analysis, requirements monitoring and controlling key processes include approving baseline requirements, managing changes to requirements, monitoring requirements status, and communicating results. Once the requirements baseline is established, the person primarily responsible for the requirements ensures that they are managed and that changes to the requirements are addressed through the defined change management process. Figure 7-1 describes the process flow. Requirements Monitoring and Controlling Requirements Planning Iterative Functions Iteratively Plan Requirements Monitoring and Controlling Trace Requirements Baseline Requirements Monitor Requirements Manage Change to Requirements Approve Requirements and Communicate Document and Communicate Results Figure 7-1. Requirements Monitoring and Controlling Activities Diagram 7.2.1 Prepare for Requirements Monitoring and Controlling Requirements monitoring and controlling planning is completed during requirements management planning and considers interactions among the requirements elicitation, analysis, and evaluation domains. Because requirements monitoring and controlling activities occur across all of these domains, decisions about how requirements will be controlled and traced should be made before the creation of requirements and captured within the requirements management plan. 7.2.1.1 Set Up System for Managing Requirements and Traceability Identification of the appropriate requirements management methods and tools for a project was discussed in Section 4.2.3. In order to monitor and control requirements, a tool may be purchased or used. This tool should be made available, with the appropriate training provided to the requirements management team before initiating the elicitation and analysis domains. 44 ©2016 Project Management Institute. Requirements Management: A Practice Guide
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 14: 1 - INTRODUCTION need to understand
Page 17 and 18: 2 - REQUIREMENTS MANAGEMENT OVERVIE
Page 24 and 25: 3 - NEEDS ASSESSMENT 3 NEEDS ASSESS
Page 26 and 27: 3 - NEEDS ASSESSMENT 3.3.2 Develop
Page 28: 3 - NEEDS ASSESSMENT 3.5.3 Gap Anal
Page 31 and 32: 4 - REQUIREMENTS MANAGEMENT PLANNIN
Page 33 and 34: 4 - REQUIREMENTS MANAGEMENT PLANNIN
Page 36 and 37: 5 - REQUIREMENTS ELICITATION 5 REQU
Page 38 and 39: 5 - REQUIREMENTS ELICITATION • Re
Page 40 and 41: 5 - REQUIREMENTS ELICITATION These
Page 42: 5 - REQUIREMENTS ELICITATION 5.3.9
Page 45 and 46: 6 - REQUIREMENTS ANALYSIS open and
Page 47 and 48: 6 - REQUIREMENTS ANALYSIS elaborate
Page 49 and 50: 6 - REQUIREMENTS ANALYSIS 6.3.1.1 M
Page 51 and 52: 6 - REQUIREMENTS ANALYSIS • Use c
Page 56 and 57: 7 - REQUIREMENTS MONITORING AND CON
Page 58 and 59: 7 - REQUIREMENTS MONITORING AND CON
Page 60 and 61: 8 - SOLUTION EVALUATION 8 SOLUTION
Page 62: 8 - SOLUTION EVALUATION requirement
Page 65 and 66: 9 - PROJECT OR PHASE CLOSURE 9.1.1
Page 67 and 68: 9 - PROJECT OR PHASE CLOSURE 9.3.1
Page 69 and 70: APPENDIX X1 - CONTRIBUTORS AND REVI
Page 71 and 72: APPENDIX X2 - SUGGESTED ADDITIONAL
Page 73 and 74: APPENDIX X3 - REQUIREMENTS MANAGEME
Page 76 and 77: GLOSSARY GLOSSARY Acceptance Criter
Page 78 and 79: GLOSSARY Configuration Management.
Page 80 and 81: GLOSSARY increases. Iterations deve
Page 82 and 83: GLOSSARY Product Backlog. See backl
Page 84 and 85: GLOSSARY Root Cause Analysis. An an
Page 86: GLOSSARY User Story. A one or two s
Page 89 and 90: INDEX Communications management, 9
Page 91 and 92: INDEX PMBOK Guide, 1-2 definitions
Page 93: INDEX Surveys, requirements elicita
show all

MANAGEMENT

Create successful ePaper yourself

Delete template?

Save as template?