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

Questions 11–15

1. 11application · medium

   After a sprint review, the team receives feedback that a feature is not what the customer expected. The team has already spent significant effort on the feature. What is the most appropriate first step for the team to take?

   • AAsk the developers to decide how to fix the feature based on their technical judgment.
   • BImmediately start reworking the feature based on the feedback.
   • CAnalyze the feedback with the product owner to understand the gap and decide how to adjust the backlog.
   • DIgnore the feedback because the feature was built according to the original requirements.
   Reveal Solution Discussion Select an answer first
2. 12application · medium

   A team is working on a feature that has a high risk of integration issues with other systems. They have a CI pipeline that runs automated tests on every commit. What is the most effective way to get early feedback on integration issues?

   • ARun integration tests in the CI pipeline as soon as the code is committed.
   • BConduct a retrospective to discuss potential integration issues.
   • CAsk the product owner to review the integration points in the code.
   • DWait until the end of the sprint to run integration tests manually.
   Reveal Solution Discussion Select an answer first
4. 13expert · hard

   A team is developing a new feature that is technically complex and has many unknowns. The product owner is available for feedback, but the team is concerned that showing an incomplete feature will confuse the customer. The team has a CI pipeline with automated tests. What is the best approach to reduce risk while managing the customer's perception?

   • ARely solely on the automated tests in the CI pipeline to validate the feature's correctness.
   • BAsk the product owner to review the code in the repository to provide feedback on the implementation.
   • CWait until the feature is fully complete and polished before showing it to the customer.
   • DShow the customer a working prototype or a partial increment at the end of the first sprint to get early feedback on the direction.
   Reveal Solution Discussion Select an answer first
5. 14application · medium

   A team is building a web application for a logistics company. They have automated unit tests and a continuous integration pipeline. The product owner attends the sprint review, but the actual end users (warehouse staff) are not involved. The team notices that the warehouse staff often complain about the usability of the interface after each release. Which additional feedback source should the team engage to address this issue?

   • AThe developers, by asking them to self-review the interface for usability.
   • BThe warehouse staff, by inviting them to participate in usability testing or demos during the sprint.
   • CThe product owner, by asking them to provide more detailed acceptance criteria.
   • DThe automated tests, by adding more integration tests to the pipeline.
   Reveal Solution Discussion Select an answer first
6. 15application · medium

   A team is developing a new feature that will take two sprints to complete. The product owner wants to see the feature only when it is fully complete at the end of the second sprint. The team is concerned about this approach. What should the team recommend to ensure early and frequent feedback?

   • AWait until the end of the second sprint to demo the complete feature to the product owner.
   • BAsk the product owner to review the code in the repository at the end of the first sprint.
   • CConduct a retrospective at the end of the first sprint to gather feedback from the team only.
   • DShow the product owner a working increment at the end of the first sprint, even if it is not fully complete.
   Reveal Solution Discussion Select an answer first