While an iteration is in progress, a project manager notices a delay in the prototype.

This question belongs to the Process domain because it concerns issue management during execution. PMI’s Lexicon defines an issue log as the project artifact where information about issues is recorded and monitored. Since the prototype is already delayed during the iteration, this is no longer just a possibility or concern; it is an active issue that requires tracking and managed follow-up.

The best first action is to record the delay in the issue log and define next steps . That creates visibility, ownership, and a structured path for response, including whether cross-functional stakeholders or SMEs need to be engaged afterward. Option A may be part of the next step, but analysis should follow formal recognition of the issue. Option B is too late because waiting for a retrospective delays action on a current problem. Option C is too narrow and delegates the decision before the issue is formally assessed. PMP-style thinking favors documenting active issues promptly, then coordinating the right response based on impact, urgency, and required expertise. That makes the issue log the most appropriate first move.