Risk Register

5 minutes 5 Questions

A risk register is a central repository for identifying, documenting, and evaluating risks throughout an agile project. The risk register is a living document that is continuously updated as new risks are identified, assessed, and mitigated throughout the project lifecycle. Common elements of a risk register include risk description, likelihood, impact, risk owner, and mitigation strategies. By maintaining a comprehensive and up-to-date risk register, agile teams can better monitor risk exposure, prioritize risk mitigation efforts, and facilitate communication and collaboration around risk management activities.

Guide to Understanding and Answering Questions on Risk Register

Why Risk Register is Important:
A risk register is vital in Agile Project Management as it systematically identifies, assesses, and plans for potential risks. It fosters proactive behavior, increases communication and transparency and helps in decision-making.
What is a Risk Register:
It is a document used in project management that contains data about identified risks, including their nature, characteristics, and the plan to manage those risks.
How Risk Register Works:
Risks are identified and then assessed for their potential impact and likelihood. They are then prioritized based on these assessments. Strategies are then developed to manage each risk.
Exam Tips: Answering Questions on Risk Register:
1. Understand the basic concepts thoroughly.
2. Practice how to identify and assess risk.
3. Ensure you can explain the process of creating a risk register.
4. Demonstrate your understanding of how risk mitigation strategies are developed.
Test mode:
Start practice test

Agile Project Management - Risk Register Example Questions

Test your knowledge of Risk Register

Question 1

During the execution phase of a project, an unplanned risk occurs that was not previously identified. Which step should be taken first to ensure this risk is properly documented in the risk register?

Correct Answer: Identify the risk, assess its potential impact, and then document it in the risk register with potential mitigation strategies.

The correct first step when encountering an unplanned risk during the execution phase of a project is to identify the risk, assess its potential impact, and then document it in the risk register with potential mitigation strategies. Ignoring the risk (Answer 149072) is not appropriate since it can potentially cause significant disruption to the project. Immediately documenting the risk in the risk register without assessing its impact (Answer 149071) is also not adequate because understanding the potential consequences of the risk is an essential part of risk management. And while communicating the risk to stakeholders (Answer 149073) is important, it should be performed after the risk has been properly identified, assessed, and documented.

Question 2

As the project manager, you realize a risk event identified previously is no longer a threat to the project. What should you do in the risk register?

Correct Answer: Indicate that the risk is closed in the Risk Status Area.

The ideal action when a risk event is no longer a threat to the project is to indicate it as closed in the Risk Status Area of the risk register (Answer ID 148974). This is because the risk register should retain a complete record of all risks identified, including those that have been resolved or are no longer threats. This aids in future risk identification, analysis and response planning. It's not recommended to remove the risk (Answer ID 148975) because that would remove its historical trace. Writing a note in the Risk Response Plan area (Answer ID 148976) would not be suitable because this area is reserved for planned responses to likely risks. Also, marking the risk as active (Answer ID 148977) is incorrect as the risk is no longer a threat.

Question 3

You are implementing an IT project and a potential risk related to software applicability has been identified. You have decided the best way to respond the risk is through transferring it. How should you document this in the risk register?

Correct Answer: Document the risk response strategy in the risk response plan area.

When a risk is transferred in a project management context, this is a risk response strategy, indicating how the team plans to deal with the potential issue. Hence, the best place to document this decision would be in the 'risk response plan' area of the risk register. This is why the first answer is correct. The 'risk categorization' and 'risk identification' areas are typically used to classify and list risks respectively, but they do not explicitly address how the risk is dealt with. Documenting in the 'risk probability and impact' area would not be appropriate either as it is used to assess the likelihood and potential consequences of the risk, not the response to it.

More Risk Register questions
125 questions (total)
Start 100 question test

Other Agile Risk Management concepts

Agile Risk Adjusted BacklogClose CollaborationContinuous Risk AssessmentIterative Risk ManagementProactive Risk ManagementRisk-Based PrioritizationRisk Burndown ChartsRisk Colored User StoriesRisk Management Tools and TechniquesRisk OwnershipRisk Response StrategiesRisk RetrospectivesRisk Tolerance
All Agile Risk Management questions · Agile Project Management practice test