You manage an agile software project with strict deadlines. The client says the last deployment failed acceptance, but the development lead insists it met specifications and provides evidence of the client's specs. What should you do?

The correct answer is to review the requirements traceability matrix with the team lead and the client. This is the most effective approach because it directly addresses the discrepancy between what the client expected and what was delivered, using an objective tool. The traceability matrix links requirements to test cases and deliverables, allowing for a clear, factual discussion about whether the delivered functionality aligns with the documented and agreed-upon requirements. This helps identify if the issue is a misunderstanding, a scope creep, or a genuine defect. Convening a meeting to assign blame is counterproductive and doesn't solve the problem. Discussing only deadlines with the client doesn't address the core issue of acceptance. Requesting additional time for rework without understanding the root cause might lead to repeating the same mistake.