CAPM Practice: Determine how to conduct stakeholder communication

BAs negotiate throughout requirements work: when stakeholders have conflicting priorities, when scope must be cut due to constraints, when technical feasibility requires requirement adjustment. Effective negotiation finds solutions where all parties feel their core needs were addressed.

**Why not A:** Negotiation as a BA communication skill has nothing to do with negotiating the BA's own compensation or salary. In the context of business analysis, negotiation refers to the ability to find mutually acceptable solutions among stakeholders with competing priorities, resolve conflicts over requirements, and reach consensus on scope and trade-offs.

**Why not C:** BA negotiation skills extend far beyond vendor contract negotiations. While vendor discussions may occasionally involve a BA, the core application of negotiation is in managing competing stakeholder interests, resolving requirements conflicts, prioritizing features, and balancing business needs against technical constraints. These negotiations happen throughout every phase of a project.

**Why not D:** Negotiation for a BA is not limited to discussions with the project manager about timelines. BAs negotiate with a wide range of stakeholders including business owners, end users, developers, architects, and executives. The subjects of negotiation span requirements scope, priority, acceptance criteria, and implementation approaches, not just project schedules.