During iteration 2 of 6, the team discovers a key deliverable depends on acquiring a new device. What should the project manager do?

The correct answer is to invite stakeholders to discuss prioritization. In agile environments, new discoveries or changes often necessitate re-evaluation of the backlog and priorities. Involving stakeholders ensures that the impact of the new device requirement is understood, and the team can collectively decide how to integrate it into the current iteration or future iterations, considering its importance relative to other work. Documenting the delay in a status report is reactive and doesn't address the core issue of integrating the new requirement. Logging a risk is appropriate, but it's a step that should follow, not precede, the discussion with stakeholders to determine the best path forward. Assigning responsibility to the core team without stakeholder input might lead to misaligned priorities or an unapproved scope change.