A mandatory compliance requirement that will impact the project software is introduced during the execution phase of an iterative project. The team is aware of the compliance requirement. What should

In an iterative (agile) project, the Product Owner is responsible for maximizing the value of the product and managing the product backlog. A new mandatory compliance requirement directly impacts the product's functionality, scope, and potentially its release, making the Product Owner the primary person to assess its implications, prioritize it against other features, and make informed decisions on how to incorporate it into the product roadmap. This escalation ensures the impact is considered from a business value perspective.

Updating the product backlog item directly is a subsequent step, but the *first* action should be to involve the Product Owner to understand the full impact and prioritize it, as the PM doesn't unilaterally decide backlog prioritization.

Escalating directly to the project sponsor might be necessary later if the impact is significant enough to affect overall project viability or funding, but the Product Owner is the first point of contact for changes impacting the product itself in an agile context.

Updating the stakeholder register is an administrative task that may be necessary, but it does not address the immediate impact of the compliance requirement on the project software or its priorities.