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 best course of action is to research the source of each requirement and work with the stakeholders to resolve the conflict. This approach allows for a deeper understanding of the underlying needs and motivations behind each requirement, which can lead to a more informed resolution. Engaging with stakeholders ensures that all perspectives are considered, fostering collaboration and ultimately arriving at a solution that aligns with the project’s objectives and user needs.

Resolving conflicts at this stage prevents potential issues in later phases of the project, such as development or testing, where ambiguity could lead to dissatisfaction or project delays. By addressing the conflict early, you ensure that the requirements remain clear and coherent, promoting a smoother development process.

In contrast, deleting one of the requirements may overlook important user needs or functionalities. Ignoring the conflict or deferring the resolution to later stages, like user acceptance testing, can lead to significant complications, such as rework, budget overruns, or missed deadlines, as unresolved conflicts may manifest as bigger problems during implementation.