What is one consequence of poor requirements documentation?

The choice highlighting the higher likelihood of scope creep is accurate because poor requirements documentation can lead to misunderstandings or misinterpretations among project stakeholders. When the requirements are not clearly defined or documented, stakeholders may have different interpretations of what is needed. This ambiguity can cause the project team to make assumptions, which may result in additional work or features being added to the project. Such additions often occur without proper assessment of their impact on the original scope, leading to scope creep where the project's goals and deliverables expand beyond the initial agreement without corresponding adjustments in resources or timelines.

Conversely, clear expectations among stakeholders, increased chances of project success, and improved stakeholder communication generally stem from well-documented requirements, reinforcing the idea that good documentation is crucial for maintaining the project scope and focus.