Answer.

In business analytics, requirement prioritization is a key stage in requirements management that allows determining which of them should be implemented first to achieve maximum business value with limited resources. Main methods:

• MoSCoW (Must have, Should have, Could have, Won't have). Helps categorize requirements into four categories based on their criticality.
• 100-Dollar Test. Participants are given "100 dollars" to distribute among the requirements, voting "with money" for the most important ones.
• Eisenhower Matrix (Urgent-Important Matrix). Requirements are distributed within a matrix of important/urgent.

The choice of method depends on context, availability of stakeholders, and team maturity. Effective prioritization requires transparency of criteria and documentation of the chosen methodology in project documentation.

Key features:

• Prioritization should be open and discussed with key stakeholders
• Regular reviews of priorities should be conducted as project circumstances change
• The method should be documented to track changes

Tricky Questions.

Can prioritization methods be combined (for example, MoSCoW and 100-Dollar Test)?

Yes, and sometimes it’s even necessary! For instance, first break down the requirements using MoSCoW, and then prioritize each group with the 100-Dollar Test.

Should a business analyst independently change the priorities of requirements without consulting stakeholders?

No, any changes in priorities must definitely be discussed and documented together with key stakeholders. Autonomous changes in priorities can lead to conflicts and loss of trust.

Does the choice of prioritization method depend on the project stage?

Yes, simpler and faster methods (like the 100-Dollar Test) are suitable at early stages, while more complex methods (like MoSCoW, Kano, or Weighted Scoring) are appropriate as requirements become more detailed.

Common Mistakes and Anti-Patterns

• Ignoring the role of stakeholders in the prioritization process
• Tying priorities solely to technical feasibility without considering business value
• Absence of regular review of priorities

Real-Life Example

Negative case:

An analyst independently determined the priorities of requirements without involving the business client.

Pros: Quick decision-making, absence of unnecessary discussions.

Cons: Implemented requirements do not meet real business priorities, conflicts arose, some valuable functions were pushed to the background.

Positive case:

An analyst conducted a facilitated session with key stakeholders, jointly selecting the MoSCoW method, documenting all agreements.

Pros: High involvement of all parties, transparent effort distribution, minimizing conflicts, maintaining relevance of priorities.

Cons: Requires more time and resources for coordination.