Prioritization in business analysis frequently involves subjective evaluation processes, especially within Agile frameworks. Techniques such as MoSCoW (Must have, Should have, Could have, Won't have) are fundamental and rely on the collective judgment and consensus of stakeholders to classify requirements based on perceived business value and necessity. Similarly, other methods like the Kano model, which assesses customer satisfaction, or simple voting/dot-voting techniques, are based on opinion and preference rather than purely objective, quantifiable metrics. While objective data is incorporated when available, subjective assessment is a valid and essential component for determining the relative importance of work items.

B. False: This is incorrect because it dismisses the validity and widespread use of qualitative, consensus-driven prioritization techniques that are inherently subjective. Many critical business value judgments cannot be derived solely from objective data.

1. Agile Business Group. (2017). AgileBA® Agile Business Analysis Handbook (Version 2.0).

Section 10.4, "Prioritisation," describes the MoSCoW technique. The text explains that MoSCoW rules are applied through discussion and consensus among business and technical roles, which is a subjective process. For example, defining a 'Must Have' as something without which "the solution is not viable" requires subjective business judgment.

2. Wiegers, K., & Beatty, J. (2013). Software Requirements (3rd ed.). Microsoft Press.

Chapter 16, "Prioritizing Requirements," discusses various prioritization techniques. It explicitly categorizes methods like "pairwise comparison and rank ordering" and the "three-level scale" (high, medium, low) which rely on stakeholder judgment. The chapter states, "Prioritization is a process of negotiation, and it always involves making subjective judgments" (p. 326).

3. Leffingwell, D. (2011). Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise. Addison-Wesley Professional.

Chapter 10, "Prioritizing the Program Backlog," introduces the Weighted Shortest Job First (WSJF) model. While WSJF aims for economic objectivity, the inputs—User-Business Value, Time Criticality, and Risk Reduction/Opportunity Enablement—are often estimated based on the subjective, expert opinions of stakeholders.