A customer has given a project team several requests for new features on a product. The customer is upset that the requests have been placed in the backlog and are not currently being worked on by the team.
What should the team do next?
A.
Review the feature requests and reject the most complex ones.
B.
Organize the feature requests from simple to complex.
C.
Prioritize the requests for the next sprint.
D.
Turn the requests into user stories and prioritize them.
The team should convert the feature requests into user stories, which are actionable and aligned with agile practices. After that, the team can collaborate with the product owner and stakeholders to prioritize the user stories based on the product's value, urgency, and impact. This approach ensures that the customer’s requests are visible and prioritized based on business needs, while maintaining transparency in the backlog.
Other options are less appropriate:
A: Rejecting complex requests outright isn't aligned with customer collaboration and may damage the relationship.
B: Simply organizing by complexity doesn’t address prioritization based on value or business impact.
C: Prioritizing for the next sprint without turning them into user stories skips an important step in the agile process.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
thewalker
6Â months agoImGonnaPassIt
1Â year, 1Â month agoNervys
1Â year, 3Â months agoPetrevski
1Â year, 6Â months ago