A business analyst (BA) finds conflicting requirements gathered from several stakeholders. Aside from interviews what additional activities can the BA use to safeguard against this happening?

Reviews allow stakeholders and BAs to examine requirements documents together and identify inconsistencies or conflicts before they become entrenched. Workshops bring competing stakeholders into a facilitated session to openly discuss and reconcile differing needs, directly addressing the root cause of requirement conflicts across multiple parties.

User stories and scope modeling are documentation and scoping techniques used to define requirements, not specifically designed to surface or resolve conflicts among stakeholder inputs.

Brainstorming is a generative idea-gathering technique, and estimation is a planning activity - neither is specifically oriented toward identifying or reconciling conflicting requirements.

Item tracking is an administrative tracking technique and mind mapping is an ideation aid; neither directly facilitates conflict detection or resolution among stakeholder requirements.