During the execution of a project, the product manager receives a new product feature request from the organization's highest revenue-generating client. The team estimates the work will take three days. What should the project manager do?

In Agile methodologies, active sprints are timeboxed and their scope is protected to maintain team focus and achieve the Sprint Goal. When a new feature request is received, even from a highly valuable client, it must be added to the Product Backlog rather than disrupting the current iteration. The Product Owner prioritizes this new item based on its business value. The project manager (or Scrum Master) should facilitate the team's analysis of this request during backlog refinement. This allows the team to properly evaluate the three-day estimate and determine if the feature can be incorporated into the next sprint during the subsequent Sprint Planning event, ensuring adaptability without compromising current commitments.

A: Starting a new sprint immediately aborts or disrupts the current timeboxed iteration, violating Agile principles that protect the team's focus on the committed Sprint Goal. C: Fast-tracking is a predictive schedule compression technique. In Agile, injecting new scope into an active sprint is generally prohibited as it endangers the agreed-upon Sprint Goal. D: Running parallel sprints for a single team destroys focus, introduces severe context-switching penalties, and violates the fundamental Agile practice of working in single, sequential timeboxes.

1. Project Management Institute. (2017). Agile Practice Guide. Section 5.2.1 (Backlog Preparation) and Section 5.2.5 (Execution Practices)

pp. 58

61. (Details how new requests are placed in the backlog for future iteration planning).

2. Schwaber

K.

& Sutherland

J. (2020). The Scrum Guide. Section: The Sprint

p. 7. (States explicitly that during a Sprint

"No changes are made that would endanger the Sprint Goal").

3. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition. Section 2.8.2 (Adaptability and Resiliency)

p. 122. (Discusses responding to change through structured reprioritization rather than immediate disruption).