US Trends

when does a developer become accountable for the value of a product backlog item selected for the sprint?

A Developer never becomes individually accountable for the value of a Product Backlog item selected for the Sprint; the entire Scrum Team shares accountability for creating value every Sprint.

Direct exam-style answer

For the common Scrum/PSPO-style question:

“When does a Developer become accountable for the value of a Product Backlog item selected for the Sprint?”

The best answer is:

C. Never. The entire Scrum Team is accountable for creating value every Sprint.

This aligns with modern Scrum teaching resources that explicitly frame value as a shared accountability of the Scrum Team, not of a single Developer or role.

Why “never” is the correct option

Several Scrum learning and exam-prep sites break down this exact question and point out that none of the time-based options (Sprint Planning, Daily Scrum, or “when they can take more work”) are correct.

  • Value is not assigned to one Developer at Sprint Planning.
  • Value is not tied to individual capacity (“whenever a team member can accommodate more work”).
  • The Daily Scrum is for inspecting and adapting the plan, not for assigning value accountability to individuals.

Instead, these sources emphasize that accountability for value is collective : the Scrum Team (Product Owner, Scrum Master, Developers) together is accountable for creating value each Sprint.

How accountability actually works in Scrum

In plain terms:

  • Product Owner is accountable for maximizing product value via Product Backlog management and ordering.
  • Developers are accountable for turning Product Backlog items into a usable Increment that could be valuable each Sprint.
  • Scrum Team as a whole is accountable for creating value every Sprint and meeting the Sprint Goal.

So while individual Developers are responsible for doing the work, they are not singled out as the ones “accountable for the value” of any particular Product Backlog item.

Mini “story” to make it stick

Imagine a team finishes a new feature in a Sprint, but users don’t like it and it delivers little value. It would be misleading to say “the one Developer who coded it is accountable for its value.” In Scrum terms:

  • The Product Owner chose and shaped that item based on a value hypothesis.
  • The Developers implemented and refined it, possibly adding technical insights.
  • The Scrum Team inspected and adapted based on feedback.

If the value is low, that’s a team-level learning moment , not an individual blame moment, which is exactly why these exam questions point you to “Never. The entire Scrum Team is accountable for creating value every Sprint.”

TL;DR:
A Developer does not become individually accountable for the value of a Product Backlog item at any specific moment; value accountability lives with the Scrum Team as a whole, every Sprint.

Information gathered from public forums or data available on the internet and portrayed here.