Which of the following is a benefit of early stakeholder feedback?

Question

Options

• AIt can be gathered early and then used to make changes after the product goes to production to
• BIt allows the project manager to get a better view of the changes that will be needed for the next
• CThe developers get a better understanding of what they are building
• DThe testers get a better understanding of the test automation requirements

• A
  3% (1)
• B
  3% (1)
• C
  87% (27)
• D
  6% (2)

Explanation

Early stakeholder feedback gives developers direct insight into what stakeholders actually need, closing the gap between assumptions and reality - making C correct. When developers understand requirements clearly from the start, they avoid costly rework caused by building the wrong thing.

Why the distractors fail:

• A is backwards - the whole point of early feedback is to make changes before production, not after, since post-production changes are far more expensive.
• B focuses on the project manager's future-release planning, which is not the primary benefit of early feedback; this confuses stakeholder input with PM forecasting.
• D is too narrow - test automation requirements are a downstream concern, and early stakeholder feedback is aimed at shaping what gets built, not how it gets tested.

Memory tip: Think of early feedback as a GPS reroute - it's far better to correct your route at the start of a trip than to backtrack after arriving at the wrong destination. Developers = drivers; stakeholders = the map.

No community discussion yet for this question.