scrum-master/risk-assessment

Identify risks across four categories—technical, resource, requirement, and dependency—then score each on a probability-impact matrix. Assign a response strategy (avoid, mitigate, transfer, or accept) based on the resulting risk level.

A probability-impact matrix scores risks by likelihood (low, medium, high) against impact (low, medium, high). The intersection determines the overall risk level, helping teams prioritize which risks need immediate response plans.

Run risk assessments at project kickoff, during sprint planning, and whenever scope or dependencies change. This skill is agent-invocable, so the scrum-master agent triggers it when risk evaluation or response planning is needed.

Four standard strategies exist: avoid (change plans to eliminate the risk), mitigate (reduce probability or impact), transfer (shift to a third party), and accept (acknowledge and prepare contingency). High risks favor avoidance, while low risks are typically accepted.

Yes, dependency risks such as unstable external APIs or delayed third-party services are an explicit category. The recommended strategy for these is transfer, shifting the risk to the responsible external party where possible.