Risk Identification

The risk management activity of systematically discovering, describing, and recording all plausible project risks by applying a variety of techniques.

Key Points

  • Conducted early and revisited throughout the project or each iteration.
  • Uses methods like brainstorming, interviews, checklists, prompt lists, RBS, SWOT, and assumptions/constraints analysis.
  • Engages the project team and key stakeholders to capture diverse perspectives.
  • Outputs initial entries in the risk register: clear risk statements, causes, potential impacts, categories, and triggers.

Example

During sprint planning for a payment feature, the team holds a risk workshop and identifies items such as API rate limits, PCI compliance changes, integration defects, and resource gaps, then records each risk with an owner and next steps in the risk register.

PMP Example Question

During a workshop, the team lists uncertain events that could affect the schedule and quality, notes their causes and categories, and adds them to the risk register. Which process are they performing?

  1. Perform Qualitative Risk Analysis
  2. Risk Identification
  3. Monitor Risks
  4. Plan Risk Responses

Correct Answer: B — Risk Identification

Explanation: Compiling and documenting risks is part of identifying risks, not analyzing, monitoring, or planning responses.

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


Build complete project plans in minutes with AI

Learn how to use AI to create charters, WBSs, schedules, risk registers, and executive reports while staying in control. This course gives you prompt templates and practical workflows based on real project work. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More