You have reviewed your requirements and discovered that you have two requirements that conflict. What should you do now?

When faced with conflicting requirements, the most effective approach is to research the source of each requirement and collaborate with stakeholders to resolve the conflict. This option emphasizes the importance of understanding the underlying reasons for each requirement, as they may arise from different perspectives or needs within the organization. By engaging with stakeholders, you can gather more information that may clarify the intentions behind the requirements.

This process fosters communication, aids in identifying the root cause of the conflict, and allows for a more informed decision-making process. Resolving the conflict collaboratively ensures that all relevant viewpoints are considered and can lead to a more comprehensive and effective solution that aligns with business goals and user needs.

In contrast, simply deleting one of the requirements disregards potentially valuable insights or needs that could impact the project. Ignoring the conflict places the burden on developers, who may not have the context required to make informed decisions, potentially leading to issues later in the development process. Deferring resolution until user acceptance testing is risky, as conflicts might create disruptions and dissatisfaction if not addressed earlier in development.