CAPM Practice: Determine how to conduct stakeholder communication

MoSCoW prioritization (and similar frameworks) provides a clear, shared vocabulary for requirement importance. Communicating priority with rationale helps the team make informed trade-off decisions when constraints require scope adjustments.

**Why not A:** Letting the development team decide priority based on implementation complexity puts technical considerations ahead of business value. While complexity informs effort estimation and sprint planning, priority should reflect stakeholder needs, business impact, and strategic alignment. The BA and product owner are responsible for communicating these priorities to guide development decisions.

**Why not C:** Treating all requirements as equally important eliminates the ability to make meaningful trade-off decisions when resources are constrained. In practice, requirements vary significantly in business value, urgency, and regulatory necessity. Effective prioritization ensures that the most critical requirements are addressed first, which is essential for delivering maximum value within project constraints.

**Why not D:** Organizing requirements alphabetically provides no meaningful prioritization whatsoever. Alphabetical ordering is arbitrary and has no relationship to business value, risk, dependencies, or stakeholder needs. Effective priority communication uses frameworks like MoSCoW, weighted scoring, or business value ranking to convey the relative importance of each requirement.