Risk

An uncertain event or series of events that, if it occurs, can influence project objectives, potentially helping or harming the project outcome.

Key Points

  • Risk can be a threat (negative) or an opportunity (positive).
  • Risk management is continuous: identify, analyze, plan responses, implement, and monitor.
  • Prioritize risks by probability and impact, considering risk appetite, tolerance, and thresholds.
  • Track risks in a risk register or risk-adjusted backlog, assign owners, and define response strategies.

Example

A supplier might not deliver a critical API by Sprint 3, delaying integration (threat). Alternatively, an early beta program could speed feedback and boost adoption (opportunity). Both are uncertain events that can influence scope, schedule, or value.

PMP Example Question

Which statement best describes a project risk?

  1. A problem that has already occurred and requires immediate resolution.
  2. A certain future event that will negatively affect scope.
  3. An uncertain event or set of events that may affect project objectives positively or negatively.
  4. A variation from plan that is always reduced by adding contingency reserves.

Correct Answer: C — An uncertain event that can help or hurt project objectives

Explanation: A risk is uncertain and can have positive or negative effects on project objectives; issues are problems that have already occurred.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Eight teaching sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Run the drill before the incident runs you

Design, run and prove OT drills and tabletop exercises before an incident tests your team. OT Incident Drills and Exercises includes 24 lessons and practical exercise materials, delivered through HKSM Courses for US$47 one-time. 30-day money-back guarantee when 50% or less of the course has been consumed.

Explore the Course