A delivered module failed during user acceptance testing. You discover the failing component was built by another team and a different functionality had been approved by the business manager. What should you do?

The correct answer is to review the integrated change control process with all stakeholders. This situation indicates a breakdown in how changes are managed and communicated across teams, leading to a delivered component that doesn't meet the current requirements. Reviewing the integrated change control process helps identify the root cause of this misalignment (e.g., unapproved changes, poor communication) and ensures all stakeholders understand and adhere to the established procedures for managing changes, preventing similar issues in the future. Escalating to the PMO and director might be necessary later, but first, understand the process failure. Asking the PMO to recover costs is punitive and doesn't address the underlying process issue. Requesting dedicated business resources for testing is a reactive measure for the current problem but doesn't solve the systemic issue of misaligned requirements and unmanaged changes.