Page 208 -

11 - PROJECT RISK MANAGEMENT

11.3 Perform Qualitative Risk Analysis

The inputs, tools and techniques, and outputs in Section 11.3 of the PMBOK Guide for performing qualitative
®
risk analysis are applicable to performing qualitative risk analysis for software projects, with the following additions
and clarifications.

It is human nature to focus on the more immediate risks, but advanced risk management is used to also identify
and control the longer-term risks. Software product development needs to be sustainable, from various viewpoints:
financial, team continuity, the software design framework, and the quality of code for future changes. Risk analysis
should also look for immediate and sustained opportunities.

11.3.1 Perform Qualitative Risk Analysis: Inputs

®
The inputs for performing qualitative risk analysis in Section 11.3.1 of the PMBOK Guide are applicable to
performing qualitative risk analysis for software projects with the following additional considerations.

Additional inputs for performing qualitative risk analysis for software projects include: (a) criticality of the
software product (its impact on its users and the operational environment), (b) the effect should a risk interfere
with the completion and successful delivery of the software product, and (c) the overall effect on the producing
organization (that is, a “bet the company” project or an optional enhancement to a mature product).

11.3.1.1 Risk Management Plan

See Section 11.3.1.1 of the PMBOK Guide.
®

11.3.1.2 Scope Baseline

See Section 11.3.1.2 of the PMBOK Guide.
®

11.3.1.3 Risk Register

®
See Section 11.3.1.3 of the PMBOK Guide.

11.3.1.4 Enterprise Environmental Factors

®
See Section 11.3.1.4 of the PMBOK Guide.

11.3.1.5 Organizational Process Assets

See Section 11.3.1.5 of the PMBOK Guide.
®

200 ©2013 Project Management Institute. Software Extension to the PMBOK Guide Fifth Edition
®