Issues

Issues are confirmed, present problems or conditions affecting the project now; unlike risks, they do not require probability analysis and instead need ownership, tracking, and resolution.

Key Points

  • Issues are happening now and have certain impact on the project.
  • They are recorded in an issue log with an owner, priority, due date, and status.
  • They require immediate attention, escalation as needed, and a clear action plan.
  • They are different from risks (uncertain future events) and may lead to change requests or follow-up risks.

Example

A vendor misses a critical hardware delivery, blocking system testing. The project manager logs it as an issue, assigns the procurement lead as owner, sets a due date to secure an alternate supplier, escalates to the steering committee, and updates the schedule once a workaround is confirmed.

PMP Example Question

During Sprint 4, the payment gateway stops working in the test environment, halting integration testing. How should the project manager classify and handle this situation?

  1. As a risk; perform probability and impact analysis and update the risk register.
  2. As an issue; record it in the issue log, assign an owner and due date, and initiate resolution actions.
  3. As a change request; skip logging and move directly to the change control process.
  4. As an assumption; document it and continue with planned work.

Correct Answer: B — Issue

Explanation: The problem is already occurring and affecting work, so it is an issue that needs ownership, tracking, and immediate resolution, not a probability assessment.

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


Stop Managing Admin. Start Leading the Future!

HK School of Management helps you learn AI prompt engineering for project work. Move beyond status reports and risk logs with practical prompt frameworks for everyday tasks. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Enroll Now