What it means
Project issue management records active problems, assigns ownership, evaluates severity and impact, escalates when necessary, tracks resolution, and captures the final outcome.
Why it matters
Risks describe uncertainty; issues are already affecting the project and require explicit action, accountability, and communication.
Practical focus
- Define the definition, severity model, ownership, escalation, and closure rules for issues before work is authorized or committed
- Use a controlled issue register, resolution plans, due dates, dependencies, and decision records to make ownership, decisions, and exceptions traceable
- Review age, severity, blockers, workarounds, residual effects, and closure evidence at planned decision points rather than only at closure
- Prepare for a known security problem remaining informal until it becomes an incident with escalation, recovery, and communication paths
Common mistakes
- Treating informal agreement as durable approval
- Leaving security ownership outside the project decision structure
- Recording activity without recording the decision and its rationale
- Discovering a known security problem remaining informal until it becomes an incident only after operational handoff
Certification relevance
This subject appears in or supports the following certification bodies of knowledge: