How should the product owner prioritize a list of tasks to be accomplished?

Question

Options

• ATasks that create business value should be done first.
• BTasks that can be completed quickly should be done first.
• CTasks that reduce the product backlog should be done first.
• DTasks that enhance the functionality of a product should be done first.

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

Explanation

Business value is the core principle guiding Product Owner prioritization - the PO exists to maximize the value delivered to stakeholders, so items with the highest business impact always take precedence (A is correct).

Why the distractors are wrong:

• B (quick tasks first) describes a "low-hanging fruit" bias - speed of completion is a secondary consideration, not the primary driver; a quick task with no value shouldn't jump the queue.
• C (reduce backlog first) confuses the goal - shrinking the backlog is not an objective; delivering value is. A large backlog isn't inherently a problem.
• D (enhance functionality first) is tempting but too narrow - not all functional enhancements deliver equal business value, and non-functional items (security, compliance, infrastructure) can outrank them.

Memory tip: Think of the PO as a business investor - just like an investor funds projects with the best ROI, the PO funds sprint work with the best return in business value. If it doesn't serve the business or customer, it waits.

No community discussion yet for this question.