HKSM

A risk checklist is a prompt list used during risk identification that points teams to typical Scrum project risks, important considerations to review, and risk categories so potential threats are not overlooked.

Key Points

• Captures key considerations, common Scrum risks, and risk categories to guide risk identification.
• Used in planning, refinement, and risk workshops to ensure comprehensive coverage.
• Tailored to the organization and product; it supports, but does not replace, analysis and judgment.
• Prompts thinking across areas such as technical, schedule, stakeholder, dependency, security, and compliance.

Example

Before a new release, a Scrum team reviews its risk checklist and identifies issues such as cloud cost overruns, missing APIs from a dependent team, evolving privacy regulations, and potential vendor delays. The team logs these risks, assigns owners, and creates mitigation actions.

PMP Example Question

During iteration planning, the team uses a risk checklist. What is the primary purpose of this tool?

1. To calculate quantitative risk exposure for the iteration
2. To ensure the team reviews common risk areas and does not miss potential risks
3. To approve the risk budget for the project
4. To replace stakeholder interviews for risk identification

Correct Answer: B — Ensure comprehensive risk identification

Explanation: Risk checklists act as prompts that help teams consider typical risks and categories so potential threats are not overlooked; they do not replace other techniques or perform analysis.