Page 219 -
P. 219
11 - PROJECT RISK MANAGEMENT
11.6.1.4 Work Performance Reports
See Section 11.6.1.4 of the PMBOK Guide.
®
In addition to the reports identified in Section 11.6.1.4 of the PMBOK Guide, test reports are valuable for
®
controlling project risks. Test results associated with defective code can be analyzed to expose design flaws and
determine whether mitigating action is necessary.
11.6.2 Control Risks: Tools and Techniques
The tools and techniques for controlling risks in Section 11.6.2 of the PMBOK Guide are applicable to controlling
®
risks for software projects, with the following clarifications and additions.
11.6.2.1 Risk Reassessment
See Section 11.6.2.1 of the PMBOK Guide.
®
11
11.6.2.2 Risk Audits
®
See Section 11.6.2.2 of the PMBOK Guide.
11.6.2.3 Variance and Trend Analysis
See Section 11.6.2.3 of the PMBOK Guide.
®
11.6.2.4 Technical Performance Measurement
See Section 11.6.2.4 of the PMBOK Guide.
®
11.6.2.5 Reserve Analysis
See Section 11.6.2.5 of the PMBOK Guide.
®
11.6.2.6 Meetings
See Section 11.6.2.6 of the PMBOK Guide.
®
The following considerations also apply. Adaptive life cycle software projects incorporate many mechanisms
for dealing with change (an easily reprioritized backlog, short iterations, daily stand-up meetings, frequent
©2013 Project Management Institute. Software Extension to the PMBOK Guide Fifth Edition 211
®