A project sponsor has requested that the project manager reprioritize the team's tasks to include a feature that is not part of the minimum viable product (MVP) for the project. Although the project s

While adding to the backlog is correct, simply explaining risks to the sponsor without consulting the team first might lead to an unachievable commitment or miss crucial insights from those doing the work.

Adding directly to the iteration backlog for immediate work without team consultation or proper prioritization, and then asking the team to 'work on current tasks' is contradictory and unsustainable given the risks of burnout and delay.

The first step is to formally acknowledge and capture the sponsor's request by adding the feature to the product backlog, ensuring it's visible and can be properly prioritized against other work. Subsequently, it is crucial to meet with the team to discuss the new feature's potential impact on their current workload, capacity, and the project timeline, facilitating a collaborative and realistic assessment of how to proceed without causing burnout or delays.

Adding the feature directly to the iteration backlog bypasses proper product backlog prioritization and essential team collaboration, increasing the risk of overcommitment and negative project impacts.