Analyzing and Communicating Gaps

  • Use quality assurance tools and methods to analyze the solution's identified gaps and deltas
  • Enable stakeholders to resolve discrepancies between solution scope, requirements, and the developed solution

When validation (the prior task) finds a mismatch, this task analyzes that gap using quality assurance tools and methods to understand its actual size and nature, then communicates it clearly enough that stakeholders can make an informed decision about how to resolve it — whether that's fixing the solution, adjusting the requirement, or accepting the gap as a known limitation.

The job here isn't to unilaterally decide how to close every gap — it's to analyze and communicate clearly enough that the people with the authority to decide (stakeholders, the sponsor) can actually make that call with full information, rather than a vague "something's off" report.

Study focus: a scenario where a gap is identified but reported so vaguely that stakeholders can't actually decide how to respond to it is testing a breakdown in the communication half of this task, even if the analysis itself was accurate.

Key terms in this chapter

Gap analysis · Delta · Quality assurance tool

Previous: Validating Solution Test Results · Next: Obtaining Stakeholder Sign-Off on the Developed Solution

Try the free PMI-PBA practice questions · Take the free PMI-PBA mock exam