Which of the following is a common pitfall during requirements elicitation?

Insufficient stakeholder engagement is indeed a common pitfall during requirements elicitation. Engaging stakeholders is crucial in understanding their needs, expectations, and any potential constraints they face. When stakeholders are not adequately involved in the process, it can lead to gaps in understanding the requirements, resulting in misaligned expectations and ultimately a product that does not meet user needs.

Effective elicitation relies on collaboration and communication with all relevant stakeholders, ensuring that diverse perspectives are considered. When stakeholders lack engagement, critical insights and feedback may be missed, creating challenges later in the development process. This pitfall can be exacerbated by assumptions that stakeholders will provide feedback without prompting, which can lead to further misunderstandings and project risks.

In contrast, excessive documentation can occur when teams focus too heavily on maintaining thorough written records rather than prioritizing stakeholder interaction and feedback. Thorough testing of requirements is necessary for ensuring quality but is not a pitfall of the elicitation phase. Regular communication with project stakeholders is beneficial and essential for successful requirements elicitation as it promotes transparency and ongoing dialogue.