PMP · Question #1210
An organization is transitioning to agile. The project manager is discussing how to manage risks with the development team in light of the transition for a particular project. The team estimates the…
The correct answer is A. Create a risk register to identify, capture, review, and manage risks using a risk management. Even in an agile transition, a project manager must establish a formal process for risk management, including creating a risk register to systematically identify, capture, review, and manage all project risks.
Question
Options
- ACreate a risk register to identify, capture, review, and manage risks using a risk management
- BTrust the development team's risk estimation and inform the project sponsor that the risks will be
- CCreate a risk register and include a single generic risk, set the level to low, and then close the risk
- DCapture all the backlog entries assessed by the development team to have evidence that risk
How the community answered
(40 responses)- A78% (31)
- B13% (5)
- C3% (1)
- D8% (3)
Why each option
Even in an agile transition, a project manager must establish a formal process for risk management, including creating a risk register to systematically identify, capture, review, and manage all project risks.
Regardless of the methodology, effective risk management is crucial. During a transition to agile, establishing clear processes, such as creating a risk register and a risk management plan, ensures that risks are systematically identified and addressed, providing proper oversight even if the team initially estimates risk as low. This builds confidence and structures the new approach.
Blindly trusting the team's low-risk estimation without a formal process is irresponsible and can lead to unmanaged issues if risks materialize.
Creating a risk register with only one generic, low-level risk undermines the purpose of risk management and leaves the project vulnerable to unaddressed threats.
Capturing backlog entries is part of product development, but it does not fully encompass a comprehensive risk management process that identifies and addresses potential threats outside of immediate backlog items.
Concept tested: Agile risk management framework
Source: https://www.pmi.org/pmbok-guide-standards/foundational/agile-practice-guide
Topics
Community Discussion
4
Bao N.Apr 18, 2026A is correct and it still shows up on exams exactly like this. Even in agile, you still need a risk register to identify, capture, review, and manage risks, and the team estimating low risk does not replace the process. B and C are trap answers for anyone who thinks agile means skipping risk documentation entirely.
Fatima Z.Apr 28, 2026A is correct because even in agile you still need a risk register, just remember my acronym CARE: Capture, Assess, Respond, and Evaluate. Saw this exact scenario on my exam last month, and the trick is that agile does not mean you skip risk documentation, it just means you keep it lighter. B is the trap because trusting the team without writing anything down is a recipe for disaster, and C is just silly since you never close a risk before the work even starts.
Toby R.May 12, 2026I first leaned toward B because in agile you want to trust the team, but even on agile projects you still need a risk register to identify, capture, review, and manage risks properly. Low risk does not mean no risk register, which is why A is the right call.
Nina C.Apr 21, 2026Coming from a teaching background so I want to make sure I get this right. Even in agile where we do not use as many formal documents, we still need a risk register to identify and track risks, correct? It seems like A is the answer because regardless of the team saying risk is low, you still need to capture and manage it rather than just skipping the process entirely.