Which practice is most effective when requirements are unclear?

• A. Document assumptions and seek clarification early.
• B. Lock in a fixed scope and refuse changes.
• C. Work without reviewing changes.
• D. Set up iterative work cycles with regular stakeholder input.

Answer: (D)

When requirements are unclear, you want a process that learns and adapts as you go. Iterative work cycles with regular stakeholder input do exactly that: you deliver small, tangible increments, get real-time feedback from those who know the needs, and use what you learn to adjust priorities, designs, and acceptance criteria in the next cycle. This keeps you from building the wrong thing and reduces risk by turning ambiguity into a sequence of verifiable steps. It also helps uncover new requirements early, so changes are incorporated sooner rather than later.

Documenting assumptions and seeking clarification early is helpful for surfacing unknowns, but without ongoing feedback and adjustment, you can still drift from what stakeholders truly need. Locking a fixed scope and refusing changes eliminates the chance to learn from new information. Working without reviewing changes misses the vital stakeholder insight that guides correct prioritization.