A project manager manages multiple information technology (IT) projects in a matrix organization. The project manager schedules a meeting with one of the functional managers to coordinate testing…

While discussing with a test engineer is good, it's usually done *after* assessing the overall strategy with the project team, as the engineer alone may not have the full context or authority to solve the resource problem.

Engaging a procurement specialist for external testing is a valid option, but it should be considered after exhausting internal options and consulting with the project team, as it introduces external costs and dependencies.

The project team collectively possesses knowledge of the project scope, requirements, and potential solutions, making them the most appropriate group to brainstorm and collaboratively determine alternative strategies or approaches to ensure that testing requirements are met despite the functional manager's resource constraints. This fosters teamwork and leverages internal expertise before escalating or seeking external solutions.

Requesting a scope change to allow developers to test (implying a reduction in formal testing or a change in testing responsibilities) is a drastic step and would compromise quality control; it should only be considered as a last resort and often requires further justification and analysis.