During a sprint review, a customer provides feedback that a new reporting feature is too complex and they only need a simplified version. The team has already spent most of the sprint implementing the complex version. What should the team do with this feedback?

Analyze the feedback, discuss it with the product owner, and adjust the product backlog to reflect the simplified requirement.

Complete the complex version as planned and add the simplified version as a new feature in a future sprint.

Ignore the feedback because the feature is almost complete and the customer will adapt.

Ask the developers to decide whether the feedback is valid, since they know the technical implementation best.

When should feedback be gathered in an agile project to ensure it is early and frequent?

At the beginning of the project only

Only at the end of each release

Continuously throughout the development cycle

A team is working on a critical feature for a healthcare application. The feature has high regulatory and usability requirements. The team plans to get feedback from the product owner only at the sprint review. What is the best way to ensure feedback is early and frequent for this high-risk feature?

Wait for the sprint review to get feedback, as this is the standard agile practice.

Ask the developers to self-review the feature against the requirements.

Defer feedback until the end of the project when the feature is fully integrated.

Schedule a dedicated feedback session with the product owner mid-sprint to review a prototype or early build.

Certified Tester Foundation Level Agile Tester

Domain 1Objective 3

Early and Frequent Feedback CT-AT Practice Questions (Page 5)

Part of the Agile Software Development domain, which makes up ~37% of our current practice bank.

24questions here

5free pages

5concepts

Questions 21–24

21application · medium
During a sprint review, a customer provides feedback that a new reporting feature is too complex and they only need a simplified version. The team has already spent most of the sprint implementing the complex version. What should the team do with this feedback?
Select an answer first
22foundation · easy
When should feedback be gathered in an agile project to ensure it is early and frequent?
Select an answer first
23foundation · easy
In an agile project, which group provides feedback on the usability and value of a feature?
Select an answer first
24application · medium
A team is working on a critical feature for a healthcare application. The feature has high regulatory and usability requirements. The team plans to get feedback from the product owner only at the sprint review. What is the best way to ensure feedback is early and frequent for this high-risk feature?
Select an answer first

Finished these 4 questions?

Review the revealed explanations, or continue through the curriculum.

No more pagesBack to CT-AT

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by ISTQB. “CT-AT” is a trademark of its owner, used for identification only.

Early and Frequent Feedback CT-AT Practice Questions (Page 5)

Questions 21–24

During a sprint review, a customer provides feedback that a new reporting feature is too complex and they only need a simplified version. The team has already spent most of the sprint implementing the complex version. What should the team do with this feedback?

When should feedback be gathered in an agile project to ensure it is early and frequent?

In an agile project, which group provides feedback on the usability and value of a feature?

Keep studying — Agile Software Development