An agile team has started a new project. When should the project manager schedule the team's first retrospective?

The first retrospective should be scheduled when the team reaches a major milestone, such as the end of the first iteration or sprint. This allows the team to reflect on their initial processes, identify what went well, and pinpoint areas for improvement early in the project lifecycle. Waiting for "a few weeks" is too vague and might delay critical feedback. Waiting for a "monumental increment" or "release" could mean delaying feedback until significant issues have compounded. While progress is good, retrospectives are for continuous improvement, not just when problems arise.