CAPM Practice: Determine how to gather requirements

Requirements conflicts occur when requirements from different stakeholders or categories contradict each other. Resolution requires understanding root needs, identifying what's truly important to each party, and facilitating compromise — often finding solutions that address all underlying needs.

**Why not A:** Requirements conflict is not about timing or deadlines for submission. While late requirements can cause project issues, the term "requirements conflict" specifically refers to situations where two or more requirements contradict each other or cannot be simultaneously satisfied. Submission timing is a process management concern, not a conflict between requirements themselves.

**Why not B:** Conflicting technical terminology is a communication issue, not a requirements conflict. While inconsistent terminology can cause confusion and should be addressed through a project glossary, a true requirements conflict occurs when the substance of two or more requirements is mutually exclusive or contradictory, regardless of the terms used to describe them.

**Why not C:** Disagreement between the development team and the business analyst is an interpersonal or organizational conflict, not a requirements conflict. Requirements conflict is a property of the requirements themselves, where two or more stated requirements cannot both be fulfilled. Team disagreements may arise from requirements conflicts, but they are not the definition of one.