An agile team consistently fails sprints because it cannot maintain the planned pace. What should the project manager do to help prevent future sprint failures?

The correct answer is to review the velocity of the team over the last several sprints and adjust the plan accordingly. Velocity is a key agile metric representing the amount of work a team can complete in a sprint. By analyzing past velocity, the project manager can gain a realistic understanding of the team's capacity and use this data to plan future sprints more accurately, thereby preventing overcommitment and subsequent failures. Switching to Kanban might address flow but doesn't directly solve the underlying issue of unrealistic sprint planning. Replacing team members or negotiating scope changes are drastic measures that don't address the immediate problem of inaccurate sprint planning based on the current team's capabilities. Approving overtime is a short-term fix that can lead to burnout and does not resolve the root cause of consistent sprint failures.