PMP Practice: Recommend options for improvement based on quality gaps

Since the root cause has already been identified as inconsistent documentation from the infrastructure team, the most effective next action is to address that root cause directly by bringing the two teams together to establish a shared standard. This collaborative approach resolves the underlying issue and prevents future defects. The team has done the analysis work—now they need to implement a solution. Facilitating cross-team collaboration to create consistency is the appropriate response to close the quality gap.

**Why not A:** Escalating to the project sponsor and requesting additional QA resources treats the symptom rather than the root cause. The team has already identified inconsistent API documentation as the primary cause, so adding more QA resources would not fix the underlying documentation problem.

**Why not B:** Adding a new quality metric to track defect rates is a monitoring action, not a corrective action. While tracking metrics is useful, it does not address the identified root cause of inconsistent documentation. The team needs to solve the problem, not just measure it more precisely.

**Why not C:** Updating the risk register documents the issue but does not directly resolve it. Since the root cause is already known, the appropriate next step is to take corrective action rather than continuing to document and plan. A mitigation plan for future sprints defers action when the team can address the cause now.