After completing the first of six iterations, the team's velocity was 50%. In the retrospective, the team determines the complexity was underestimated. What should the project manager do?

The correct answer is to meet with the team to agree on internal actions to address the problem. This aligns with agile principles, where the team is self-organizing and empowered to identify and resolve issues. A retrospective is precisely the forum for the team to discuss what went wrong (underestimated complexity) and collaboratively determine how to improve for future iterations. Recording the issue and escalating it to the project sponsor is premature and undermines team autonomy. The team should first attempt to resolve issues internally. Requesting assistance from a technical manager might be a later step if the team cannot resolve the issue, but the initial response should be team-centric. Replacing team members is a drastic and disruptive measure that does not address the root cause of underestimation and is contrary to fostering a supportive team environment.