Which requirement prioritization technique is commonly used in business analysis?

The MoSCoW prioritization technique is particularly valuable in business analysis as it helps stakeholders categorize requirements based on their importance and urgency. The acronym stands for Must have, Should have, Could have, and Won't have this time. This method allows teams to focus on the most critical requirements that must be met for project success, while also facilitating discussions about trade-offs and resource allocation.

By using MoSCoW prioritization, business analysts can ensure that the requirements gathering process is organized and that the development team focuses on delivering maximum value within the constraints of time and resources. This technique aids in managing stakeholder expectations and aligning the project objectives with business goals effectively.

Other techniques listed serve different purposes. For instance, the Five Whys is a problem-solving method used to identify root causes, rather than prioritizing requirements. The Fishbone Diagram helps in identifying potential causes of a specific issue but doesn't assist with requirements prioritization. Root Cause Analysis focuses on finding the source of a problem rather than establishing the priority of various requirements. Thus, MoSCoW stands out as the most relevant technique for requirement prioritization in business analysis.