In a Scrum project, when would a requirement get added to the Product backlog?

Question

Options

• AWhen it is developed, but cannot yet be released.
• BWhen the team works on it for a particular release.
• CWhen the customer requests a new requirement.

• A
  2% (1)
• B
  5% (3)
• C
  93% (55)

Explanation

Option C is correct because the Product Backlog is a living, ordered list of everything that might be needed in the product, and items are added to it as soon as a stakeholder or customer identifies a new need - long before any development work begins. Option A is wrong because that describes a completed but unreleased increment, not a backlog addition event; work that's done but not released is tracked differently (e.g., in a release pipeline or as a "Done" increment). Option B is wrong because by the time the team works on a requirement, it has already been in the backlog, refined, estimated, and selected into a Sprint - adding it at that point would be too late.

Memory tip: Think of the Product Backlog as a wish list - you add items to a wish list when you want something, not when you're already using it. The customer's request = the wish = the backlog entry.

No community discussion yet for this question.