CS615 - Software Project Management: Risk and Change Management MCQs with Answers & Solutions | VU SIGMA – Page 4 of 11

Question 1

Discuss the roles of risk mitigation, risk monitoring, and contingency planning in software risk management. Explain how a project manager transitions from risk mitigation to contingency planning when a risk materializes, using high staff turnover as an example.

Accepted Answer

1. Risk Mitigation (Problem Avoidance): Working proactively to reduce the likelihood of a risk occurring. For high staff turnover, this involves meeting with staff to resolve workplace or compensation issues and organizing cross-functional teams to disperse project knowledge.
2. Risk Monitoring (Tracking): Assessing whether predicted risks occur and evaluating the effectiveness of mitigation steps. The manager tracks team morale, interpersonal relationships, and job market trends.
3. Contingency Planning (Problem Recovery): Alternative plans put into action when mitigation fails and the risk becomes a reality.

Transition Example: If key staff members resign, the manager triggers the contingency plan. This involves immediately moving backup staff to critical roles, refocusing resources to fully staffed tasks, and transitioning departing staff to a temporary 'knowledge transfer mode' to capture their expertise before they leave.

Question 2

Which of the following is defined as a project tracking activity with the primary objective of assessing whether predicted risks do, in fact, occur?

Accepted Answer

Risk Monitoring

Answer

Risk Identification

Answer

Risk Mitigation

Answer

Risk Analysis

Question 3

Differentiate between risk mitigation and risk monitoring, and describe the three initial objectives of risk monitoring.

Accepted Answer

Risk mitigation is a proactive problem avoidance activity performed to reduce the likelihood of risks. Risk monitoring is a tracking activity performed as the project proceeds. The three initial objectives of risk monitoring are: 1) to assess whether predicted risks do, in fact, occur; 2) to ensure that risk aversion steps are properly applied; and 3) to collect data for future risk analysis.

Question 4

What is software safety and hazard analysis, and when should these SQA activities be conducted during software engineering?

Accepted Answer

Software safety and hazard analysis focus on identifying and assessing potential hazards that could cause an entire system to fail. These SQA activities must be conducted early in the software engineering process so that safety features can be designed directly into the system to eliminate or control those hazards.

Question 5

Which of the following is a primary objective of software safety and hazard analysis, and when should these activities ideally be conducted?

Accepted Answer

To identify and assess potential hazards early in the software engineering process so that design features can eliminate or control them.

Answer

To perform exhaustive testing during the system implementation stage to locate coding syntax errors.

Answer

To calculate source lines of code (SLOC) after the system has been fully delivered to the client.

Answer

To manage the project budget and financial plans after the final deployment of the software.

Question 6

Distinguish between development process risks and product-related risks in software project management, providing two examples for each category.

Accepted Answer

Development process risks relate to the execution of the project, such as developer errors and natural disasters. Product-related risks focus on the quality and specifications of the software, such as incomplete requirements and product complexity.

Question 7

Which of the following is classified as a development process risk rather than a product-related risk?

Accepted Answer

Disgruntled employees and developer errors

Answer

Complexity of the software product

Answer

Incomplete and unclear requirements

Answer

Unclear project deliverables and objectives

Question 8

In the context of software engineering, describe Robert Charette's three conceptual underpinnings of risk and explain how each manifests in software projects.

Accepted Answer

1. Future Happenings: Risk focus is on the future, asking how current decisions can prevent future software project failures.
2. Change: Software projects are highly dynamic, meaning changes in customer requirements, technologies, and target systems must be constantly managed.
3. Choice: Project teams must make difficult decisions regarding methods, tools, staff sizes, and quality standards, all of which introduce logical uncertainty.

Question 9

Which of the following are the three conceptual underpinnings of risk identified by Robert Charette in the context of software engineering?

Accepted Answer

Future, Change, and Choice

Answer

Certainty, Stability, and Execution

Answer

Past Performance, Code Size, and Developer Capability

Answer

Planning, Organizing, and Controlling

Question 10

In software engineering, Robert Charette defines risk through three conceptual underpinnings. Which of the following options correctly identifies these three conceptual underpinnings?

Accepted Answer

Future, Change, and Choice

Answer

Planning, Scheduling, and Budgeting

Answer

Scope, Time, and Quality

Answer

Avoidance, Monitoring, and Management

Risk and Change Management

📖 Related CS615 - Software Project Management Curriculum Units