Stakeholders commonly face challenges in prioritizing requirements due to:

Question

Options

• Alack of knowledge.
• Bproject time constraints.
• Cdifferent perceived values.
• Dinability to work with others.

• A
  3% (1)
• B
  5% (2)
• C
  89% (34)
• D
  3% (1)

Explanation

Stakeholders prioritize requirements based on their own perspectives, roles, and goals - meaning each person genuinely believes their needs matter most. Because different stakeholders perceive value differently (a CFO values cost savings while a user values usability), reaching consensus on priority becomes the core challenge, making C correct.

Why the distractors are wrong:

• A (lack of knowledge) - Stakeholders typically do know their domain well; the problem isn't ignorance but conflicting viewpoints among knowledgeable parties.
• B (project time constraints) - Time pressure is a project management challenge, not a root cause of prioritization disagreements among stakeholders.
• D (inability to work with others) - This implies a personality or skill deficiency, but prioritization conflicts arise even among highly collaborative teams due to structural differences in goals.

Memory tip: Think of three stakeholders - the CEO (profit), the customer (ease of use), and legal (compliance). None are wrong or ignorant; they just value different things. "Different values → different priorities" is the essence of C.

No community discussion yet for this question.