A project sponsor has asked the project manager to reprioritize the team's tasks to include a feature that is not part of the project's minimum viable product (MVP). Although the sponsor strongly wants the feature, adding it could cause team burnout and/or delay the release. How should the project manager address this situation?

The correct approach involves acknowledging the sponsor's request while managing expectations and protecting the team. First, adding the feature to the product backlog ensures it's formally captured for future consideration. Next, explaining the consequences (burnout, delays) to the sponsor provides transparency and helps them understand the impact of their request, aligning with the "inspect and adapt" principle of agile. Finally, suggesting inclusion in the next iteration allows the team to complete current commitments without disruption, preventing burnout and maintaining a sustainable pace. The other options are less ideal because: Including the feature in the iteration backlog immediately without discussion or consequence explanation could lead to overcommitment and burnout. Meeting to decide how to deliver it within the current iteration is risky given the potential for burnout and delays, especially if it's not part of the MVP. Asking the team to deliver it in the current iteration after explaining consequences still pressures them and risks the negative outcomes.