One of the modules delivered by the project failed during user acceptance testing (UAT). The project manager realizes that the component that failed the functional tests was created by another team an

The situation describes a failure due to a component developed by another team with a functionality *different* from what was approved by the business manager. This indicates a breakdown in how changes were managed and integrated across teams and approvals, making a review of the integrated change control process crucial.

Escalation might be necessary eventually, but first, the project manager needs to understand the root cause of the misalignment within the project's own processes, specifically related to change control and inter-team coordination.

Attempting to recover costs prematurely is punitive and does not address the underlying process failure that led to the incorrect functionality being developed and approved.

Requesting dedicated business resources for testing doesn't address the root cause of the functionality misalignment or the breakdown in the change management process between teams and approvals.