Risk Management & Mitigation Flashcards
7 cards from real ICP practice questions. Tap to flip, then mark Knew It or Still Learning โ missed cards come back until you master them.
Read the first 7 Risk Management & Mitigation flashcards as text
Which agile scaling framework explicitly uses a 'Program Risk Board' to manage risks across multiple teams?
Answer: SAFe (Scaled Agile Framework)
SAFe uses a Program Risk Board (often via ROAM: Resolved, Owned, Accepted, Mitigated) at the PI Planning event to manage cross-team risks.
The ROAM acronym in SAFe risk management stands for:
Answer: Resolved, Owned, Accepted, Mitigated
ROAM categorizes each risk as Resolved (no longer a risk), Owned (someone takes responsibility), Accepted (team acknowledges and proceeds), or Mitigated (action taken to reduce impact).
An agile team chooses to build a proof of concept (PoC) before committing to a full implementation. This is an example of:
Answer: Risk mitigation through early validation
A PoC reduces technical and feasibility uncertainty before a full investment is made, which is a proactive mitigation strategy.
Which of the following best represents a 'residual risk'?
Answer: The remaining risk exposure after a response has been applied
Residual risk is the remaining level of risk that persists after mitigation actions have been implemented; teams must decide whether to accept it.
When should risk identification ideally begin on an agile project?
Answer: During the product vision and release planning stages
Early risk identification during vision and planning allows teams to build risk responses into the roadmap and avoid costly surprises later.
A team decides to accept a low-probability, low-impact risk without any specific action. This is called:
Answer: Passive risk acceptance
Passive acceptance means the team acknowledges the risk but takes no proactive action, choosing to deal with it only if it occurs.
Which agile value or principle most supports a culture of open risk reporting?
Answer: Transparency as a pillar of empirical process control
Transparency, one of Scrum's three pillars, ensures risks and impediments are visible to all stakeholders, enabling timely inspection and adaptation.