Problem Detection and Resolution (Domain VI) contains the focus areas & quick notes on this topic which will help you to pass the PMI-ACP® exam offered by PMI. Domain VI Problem Detection and Resolution accounts for 10% (~12 questions) of all questions to be found on the Exam. Below is a collection of the key knowledge addressed in Problem Detection and Resolution and the tasks related to the domain (Continuously identify problems, impediments, and risks; prioritize and resolve in a timely manner, monitor and communicate the problem resolution status, and implement process improvements to prevent them from occurring again).
Focus Areas for Problem Detection and Resolution
Refactoring: Refactoring is the process of restructuring existing internal computer code without changing its external behaviors.
Burnup Charts: Used to track the project’s progress by comparing total scope against completed work over time. One line is the scope and the other is completed work. Can also help track scope changes.
Burn down Charts: Compares how much work is left to do with the timeline and helps the team predict when they will complete the work.
Risk Burn down Charts: Shows risk exposure over time. The lines should be trending down as risk is mitigated; if not, the team will have to allocate some time to mitigate the risks.
Architectural Spike: Quick experiment (Focus on architecture with high risk) used to help the team answer a question and determine a path forward
Risk-adjusted backlog: Value-generating business features and risk-reduction actions.
Risk-based spikes: Quick experience used to help the team answer a question and determine a path forward.
Risk burn-down charts: A chart where the risk to project success associated with each feature is displayed.
Risk-adjusted backlog
A backlog that is adjusted to accommodate risk that needs to be mitigated while still accomplishing work on the features.
- Risks are assessed by risk probability (how likely it occurs) and risk impact (how severe the risk impact is):
- Risk Severity = Risk Probability x Risk Impact
- Risk probability can be a percentage value or a number on a relative scale (the higher the more likely)
- Risk impact can be dollar value or a number on a relative scale (the higher the more costly to fix)
Discover and identify risks:
Brainstorming and information-gathering techniques
- Delphi technique
- Checklist analysis
- Diagramming techniques
- Assumption analysis
- SWOT analysis
- Expert judgment
Risk categories:
- Business risk: e.g., value, priority, satisfaction
- Technical risk: e.g., code complexities/technical uncertainties
- Logistical risk: e.g., scheduling, resourcing
Strategies for Negative Risks: Avoidance, Transference, Mitigation
Strategies for Positive Risks or opportunities: Exploit, Share, Enhance
Strategies for Both Threats and Opportunities: Contingency Reserve & Management Reserve
Monitoring and Controlling Risks: 5 Whys, Fishbone Diagram Analysis, Divide and conquer, Expert judgment, Simulation, Brainstorming, Metaphors, Trial and error, Spikes, Trend analysis, Probing, Sandboxing, Project risk response audits, Periodic project risk reviews, Technical performance measurement, Additional risk response planning, Workarounds, Reserve analysis & Daily status meetings.
