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
  7% (2)
• B
  3% (1)
• C
  90% (26)

Explanation

Option C is correct because the Product Backlog is a living list of everything the product might need, and new items are added whenever a stakeholder - most commonly the customer or Product Owner - identifies a new requirement or need. The backlog exists precisely to capture these requests at any point in the project, not just during sprints.

Option A is wrong because "developed but not yet released" describes an increment that is Done but not yet deployed - it has nothing to do with when items enter the backlog. Option B is wrong because working on a requirement during a sprint means it has already been selected from the backlog into the Sprint Backlog - it's too late in the process for the item to be "added" to the Product Backlog.

Memory tip: Think of the Product Backlog as a customer wish list - items go on the list the moment someone asks for them, not when you start shopping or after you've already bought something.

No community discussion yet for this question.