Page 204 -
P. 204
11 - PROJECT RISK MANAGEMENT
The software project manager needs to ensure that risk management procedures, frequency of reporting
cycles, and a risk register are established at the beginning of the project. The risk register can be as simple as a
spreadsheet or whiteboard with annotated note cards or stories attached. For large projects and critical software
products, specialized software tools aid in managing the outputs from planning risk management.
11.2 Identify Risks
®
The inputs, tools and techniques, and outputs for identifying risks in Section 11.2 of the PMBOK Guide are
applicable for identifying risks for software projects.
11.2.1 Identify Risks: Inputs
The inputs for identifying project risk in Section 11.2.1 of the PMBOK Guide are applicable for identifying
®
software project risks with the additional considerations in Section 11.2.1.14 in this Software Extension.
11.2.1.1 Risk Management Plan
See Section 11.2.1.1 of the PMBOK Guide.
®
11.2.1.2 Cost Management Plan
See Section 11.2.1.2 of the PMBOK Guide.
®
11.2.1.3 Schedule Management Plan
See Section 11.2.1.3 of the PMBOK Guide.
®
11.2.1.4 Quality Management Plan
See Section 11.2.1.4 of the PMBOK Guide.
®
11.2.1.5 Human Resource Management Plan
®
See Section 11.2.1.5 of the PMBOK Guide.
11.2.1.6 Scope Baseline
®
See Section 11.2.1.6 of the PMBOK Guide.
196 ©2013 Project Management Institute. Software Extension to the PMBOK Guide Fifth Edition
®
