Benefits of Early and Frequent Stakeholder Feedback CTFL Practice Questions (Page 3)

Questions 11–15

1. 11foundation · easy

   How does early defect detection lower overall project risk?

   • ABy reducing the amount of rework needed later in the project
   • BBy reducing the need for stakeholder involvement in testing
   • CBy ensuring that all defects are fixed before the design phase
   • DBy increasing the number of defects found during user acceptance testing
   Reveal Solution Discussion Select an answer first
2. 12application · medium

   A team is starting a project to develop an e-commerce website. The business analyst has created the initial requirements document. To reduce the risk of defects being discovered late in the project, which action should the team take?

   • AProceed directly to development and rely on system testing to catch any issues in the requirements.
   • BOrganize a requirements review workshop with stakeholders from marketing, sales, and IT support to validate the document before development.
   • CWait for the user acceptance testing phase to involve stakeholders in validating the requirements.
   • DAsk the development team to informally read the requirements and start coding, assuming they understand the business needs.
   Reveal Solution Discussion Select an answer first
4. 13foundation · easy

   How do frequent feedback loops contribute to timely issue resolution?

   • ABy identifying and addressing problems early in the development cycle
   • BBy postponing all discussions until the end of the project
   • CBy reducing the number of stakeholders involved in the project
   • DBy requiring stakeholders to approve every minor change
   Reveal Solution Discussion Select an answer first
5. 14application · medium

   A team is using an agile approach to develop a new inventory management system. The product owner wants to ensure that stakeholder feedback is continuously incorporated into the development process. Which practice would best achieve this?

   • AAsk the development team to infer stakeholder preferences from the initial requirements document.
   • BHave stakeholders provide feedback only at the end of the project to avoid disrupting the team.
   • CInclude stakeholders in the sprint review meetings and use their feedback to update the product backlog.
   • DSend a survey to stakeholders once at the beginning of the project to collect all their requirements.
   Reveal Solution Discussion Select an answer first
6. 15application · medium

   A development team is building a customer relationship management (CRM) system. The project manager wants to ensure that stakeholder feedback is incorporated regularly to keep the product aligned with business needs. Which practice best supports frequent feedback cycles?

   • AHold a brief feedback session with key stakeholders at the end of each two-week iteration to review progress and adjust priorities.
   • BCollect all stakeholder feedback in a single comprehensive meeting at the end of the project.
   • CAsk stakeholders to submit feedback via email whenever they think of something, without a structured timeline.
   • DHave the project manager gather feedback from stakeholders and present it to the team only when major milestones are reached.
   Reveal Solution Discussion Select an answer first