HKSM
Risk Meeting
A session the Product Owner calls to prioritize risks with the Scrum Core Team, optionally including relevant business stakeholders.
Key Points
- Purpose is to rank risks and decide next actions.
- Attendees are the Scrum Core Team; the Product Owner may invite business stakeholders as needed.
- Outputs include an ordered risk list, assigned owners, and updates to the Product Backlog or Sprint Backlog.
- Held when new or significant risks arise, or on a regular cadence; keep it timeboxed and focused.
Example
The Product Owner learns of a possible regulatory change. They call a risk meeting with the Scrum Core Team and invite a compliance stakeholder. The group assesses probability and impact, ranks the risks, creates a mitigation spike and a contingency task, assigns owners, and updates the Product Backlog.
PMP Example Question
To prioritize several new risks before the next Sprint, what should the Product Owner do?
- Add the risks to the impediment list and wait for the Scrum Master to resolve them.
- Convene a Risk Meeting with the Scrum Core Team and, if helpful, invite business stakeholders.
- Extend the Daily Scrum to allow deep risk discussion and ranking.
- Ask Developers to address risks ad hoc during the Sprint without formal prioritization.
Correct Answer: B — Hold a PO-led session with the Scrum Core Team (and optional stakeholders) to prioritize risks.
Explanation: A Risk Meeting is specifically for prioritizing risks with the Scrum Core Team; Daily Scrum is not for deep dives, and ad hoc handling or parking risks as impediments is inappropriate.
