PMP · Question #974
A development team member learned that one of the product features delivered in the last sprint would have greater business value if a small enhancement was made to the feature. What should the…
The correct answer is B. Discuss this feature in the next sprint planning meeting. A newly identified enhancement for a delivered feature should be introduced for consideration in the next sprint planning meeting to determine its priority and integration into the backlog.
Question
A development team member learned that one of the product features delivered in the last sprint would have greater business value if a small enhancement was made to the feature. What should the project manager do next?
Options
- AConduct another sprint planning meeting and add the necessary story.
- BDiscuss this feature in the next sprint planning meeting.
- CDiscuss this feature during the upcoming retrospective meeting.
- DAdvise the team member to better prepare before sprint planning.
How the community answered
(29 responses)- A7% (2)
- B76% (22)
- C14% (4)
- D3% (1)
Why each option
A newly identified enhancement for a delivered feature should be introduced for consideration in the next sprint planning meeting to determine its priority and integration into the backlog.
Conducting an *another* sprint planning meeting just for a small enhancement disrupts the sprint rhythm and is generally not an agile best practice unless the change is critical and urgent enough to warrant stopping the current sprint.
When a new enhancement or change is identified for a product feature, even a small one, it should be brought to the sprint planning meeting. This allows the team, product owner, and other stakeholders to discuss its business value, prioritize it against other backlog items, and decide if it should be added to a future sprint.
Retrospective meetings are for process improvement and team reflection, not for discussing new product features or enhancements to be implemented.
Advising the team member to better prepare is dismissive and doesn't address the valid suggestion for a value-adding enhancement, which could not have been known prior to the feature's delivery.
Concept tested: Agile change management; Sprint planning
Source: https://www.scrum.org/resources/what-is-sprint-planning
Topics
Community Discussion
5
Wesley A.Jul 5, 2026B is correct. I actually picked C on my first attempt because I thought any improvement discussion belonged in the retrospective, but that cost me. The retrospective is for process improvements, not for adding new work items. Since the enhancement is really a new product backlog item, it belongs in the next sprint planning meeting where the team can prioritize and pull it in if it makes sense.
Mei-Ling H.Jul 5, 2026B is correct because the enhancement is really a new request that belongs in the Product Backlog first, then gets prioritized during the next sprint planning meeting. The key word is "would have greater value" which means it is not yet committed work. C is tempting because the retrospective is the next agile ceremony, but that meeting is for process improvement, not for adding features. One thing I want to clarify, does the enhancement story need to go through backlog refinement before sprint planning, or can the team bring it straight to the planning session for estimation?
Ingrid P.Jul 8, 2026Good catch on B, and to answer your question: refinement is where the team grooms and estimates the story so it is ready for planning, so skipping it means bringing an unestimated, un-groomed item into sprint planning, which defeats the purpose of having a refinement stage.
Ingrid P.Jul 4, 2026I first leaned toward C because the retrospective is where you talk about what happened in the last sprint, but that meeting is for process improvements, not for adding scope. The enhancement is really a new piece of work, and in Scrum you do not inject stories mid-sprint or call a special planning session just for this. The right move is to bring it to the next sprint planning meeting so the team can prioritize and decide whether to pull it in. Made a card on this one: retrospective equals process, sprint planning equals new stories.
Mei-Ling H.Jul 6, 2026Good card but watch the qualifier on the real exam, if the stem says the enhancement is urgent or high priority then the answer shifts to Product Owner negotiating scope with the team mid-sprint, not waiting for next planning.