Skip to content
DE
← All CTFL learning objectives

CTFL 3.2.1: Identify the benefits of early and frequent stakeholder feedback

K1

Syllabus section 3.2.1

3 original PrepBench practice questions for learning objective 3.2.1 of the CTFL 4.0 syllabus. Try the examples below and check each answer against its syllabus reference.

Practice questions

Question 1

Frequent stakeholder feedback helps the development team improve its understanding of what it is building. What does this allow the team to focus on?

  1. The features that are cheapest to implement in the current iteration
  2. The features the team's own architects consider technically most interesting
  3. The features whose acceptance criteria are already fully documented
  4. The features that deliver the most value to stakeholders and most affect identified risks
Show answer
  • The features that are cheapest to implement in the current iterationImplementation cost is not the basis the syllabus names for this focus.
  • The features the team's own architects consider technically most interestingTechnical interest to the team is not the basis the syllabus names for this focus.
  • The features whose acceptance criteria are already fully documentedDocumented acceptance criteria are not the basis the syllabus names for this focus.
  • Correct answer: The features that deliver the most value to stakeholders and most affect identified risksStakeholder value and impact on identified risks are the named basis.

Frequent stakeholder feedback throughout the SDLC helps the development team improve their understanding of what they are building. It allows them to focus on those features that deliver the most value to the stakeholders and that have the most positive impact on identified risks.

Syllabus section 3.2.1

Question 2

What is a likely consequence of little stakeholder involvement during the SDLC?

  1. Requirement changes are picked up later, but the delivered product still matches the vision
  2. The product might not meet the stakeholders' original or current vision, causing costly rework
  3. The team delivers faster, because fewer opinions have to be reconciled during development
  4. Quality problems are found at the same time, but by the test team rather than the stakeholders
Show answer
  • Requirement changes are picked up later, but the delivered product still matches the visionMissing the vision is precisely the risk; the product is not assured to match it.
  • Correct answer: The product might not meet the stakeholders' original or current vision, causing costly reworkThe product may miss the original or current vision, causing costly rework.
  • The team delivers faster, because fewer opinions have to be reconciled during developmentThe syllabus names costly rework and missed deadlines, not faster delivery.
  • Quality problems are found at the same time, but by the test team rather than the stakeholdersEarly feedback exists to communicate quality problems earlier, not merely elsewhere.

If there is little stakeholder involvement during the SDLC, the product being developed might not meet the stakeholders' original or current vision. A failure to deliver what the stakeholder wants can result in costly rework, missed deadlines, blame games, and might even lead to complete project failure.

Syllabus section 3.2.1

Question 3

What is a benefit of early and frequent stakeholder feedback throughout the SDLC?

  1. It gives the team a stable requirement baseline to design its tests against
  2. It gives stakeholders ownership of the quality of their own requirements
  3. It lets the team review the requirement specification less often
  4. It prevents misunderstandings about requirements and gets changes in earlier
Show answer
  • It gives the team a stable requirement baseline to design its tests againstFrequent feedback keeps requirements understood and changed earlier; it does not freeze them into a baseline.
  • It gives stakeholders ownership of the quality of their own requirementsThe feedback improves the development team's own understanding of what it is building; ownership does not move.
  • It lets the team review the requirement specification less oftenStakeholder feedback is obtained through static testing, including reviews, so it does not displace them.
  • Correct answer: It prevents misunderstandings about requirements and gets changes in earlierIt prevents requirement misunderstandings and gets changes understood and implemented earlier.

Frequent stakeholder feedback throughout the SDLC can prevent misunderstandings about requirements and ensure that changes to requirements are understood and implemented earlier. This helps the development team improve its understanding of what it is building and lets it focus on the features that deliver the most value and have the most positive impact on identified risks.

Syllabus section 3.2.1

Original PrepBench practice material, not official exam questions or exam dumps. PrepBench is independent and is not affiliated with or endorsed by ISTQB®.

Glossary terms in this chapter

Practice chapter 3Take a CTFL mock exam