Page 203 - DCAP304_DCAP515_SOFTWARE_PROJECT_MANAGEMENT

Unit 10: Risk Management

 Risk Control Notes
 coming up with techniques and strategies to mitigate the highest ordered risks
 implementing the strategies to resolve the high order risks factors
 monitoring the effectiveness of the strategies and the changing levels of risk
throughout the project.

Task Discuss with your class fellows about different types of risks items and we can
define lists the following top 10 software risk items:

1. Personnel Shortfalls
2. Unrealistic schedules and budgets
3. Developing the wrong functions and properties
4. Developing the wrong user interface
5. Gold-plating

6. Continuing stream of requirements changes
7. Shortfalls in externally furnished components
8. Shortfalls in externally performed tasks

9. Real-time performance shortfalls
10. Straining computer-science capabilities

10.7 Metrics in Risk Management

There are many metric sets proposed throughout in Software Engineering literature, and
following is one very simple set of “core” attributes which drive the list of measures to collect:
 Size
 Effort
 Schedule

 Software quality
 Rework
Most metric sets deal with a variation of these attributes and are chosen to help project managers
gain insight into their product (size, software quality, rework), process (rework, software quality)
and project (effort, schedule).

10.7.1 Identifying Risks with Metrics

One simple measure that can be collected is staff level, sometimes called personnel, which
counts the total number of software personnel available for a project. At initial risk identification,
this measure can be used in a feasibility analysis and compared against the estimated staffing
level. The results can give managers an indication of whether they will have enough personnel
for a project or whether they will have to start looking for new team members.

LOVELY PROFESSIONAL UNIVERSITY 197