A project manager has run an agile project for six months; over the last two iterations velocity has dropped due to a new technology needed for the product. What should the project manager do to continue delivery and return to expected velocity?

The correct answer is to use retrospectives. Retrospectives are a core agile practice designed for continuous improvement. They provide a structured opportunity for the team to discuss what went well, what didn't, and what can be improved. In this scenario, the retrospective would be the ideal forum to analyze the impact of the new technology, identify skill gaps that are contributing to the velocity drop, and collaboratively decide on adjustments to the team's approach or composition. Requesting additional funding or replacing team members are reactive measures that don't address the root cause or leverage the team's problem-solving capabilities. Reprioritizing the backlog might offer a temporary fix but doesn't resolve the underlying issue of the new technology's impact on velocity.