A development manager started implementation activities for a product deployment to more than 600 users.

When severe anomalies are discovered just before final release, the test leader’s first responsibility is to communicate the risk to the appropriate project authority. The development manager owns release execution decisions, so the test leader should notify the manager and recommend delaying the release until the anomalies are evaluated and resolved. Root cause analysis and corrective action are important, but they come after immediate risk communication and release control. Requiring developers to fix the anomalies immediately may be necessary later, but the test leader should not bypass release decision processes. Notifying users directly may create confusion and may exceed the test leader’s authority. Severe anomalies can affect customer operations, so release delay should be recommended.

================