CAPM Practice: Determine how to gather requirements

Conflict resolution in requirements starts with understanding the underlying needs — often conflicts at the requirement level dissolve when parties understand each other's underlying goals. BAs facilitate structured dialogue to find solutions that address all parties' real needs.

**Why not A:** Documenting both conflicting requirements and leaving the decision to developers abdicates the BA's conflict resolution responsibility. Developers lack the business context to make requirements trade-off decisions, and unresolved conflicts lead to arbitrary implementation choices that may not serve business goals.

**Why not C:** Choosing requirements from the most senior stakeholder ignores the merits of each requirement and the underlying business needs. Authority does not guarantee the best solution. The BA should facilitate resolution based on business value and organizational goals, not hierarchical rank.

**Why not D:** Removing both conflicting requirements and independently finding alternatives bypasses stakeholder involvement entirely. The affected stakeholders have domain knowledge essential to crafting a good solution. The BA should facilitate negotiation among them rather than making unilateral decisions.