What is the consequence of overlooking a source of requirements?

Overlooking a source of requirements can significantly compromise the completeness and quality of the requirements gathered for a project. When key stakeholders or sources of information are ignored, there's a high likelihood that important needs, preferences, or constraints will not be captured. This can lead to requirements that do not fully address the problems or deliver the functionality expected by users or stakeholders. As a result, the final product may not meet the intended goals or satisfy user needs, which can ultimately impact the project’s success and stakeholder satisfaction.

While some may believe that requirements can simply be added later, this often leads to additional costs, delays, and complications in project timelines. It can also result in missed opportunities for creating a more robust and user-centric product from the outset. Therefore, paying attention to all sources of requirements from the beginning is crucial for ensuring a complete and effective requirements base.