How much work must a Development Team do to a Product Backlog item it selects for a Sprint?

Question

Options

• AAn equal amount of time on analysis, design, programming, testing and documentation.
• BAs much as it has informed the Product Owner will be done for every Product Backlog item it
• CAll development work and at least some testing.
• DAs much as it can fit into the Sprint. Any remaining work will be moved to a subsequent Sprint.

• A
  3% (1)
• B
  92% (34)
• C
  3% (1)
• D
  3% (1)

Explanation

Option B is correct because the Scrum framework requires the Development Team to meet its own Definition of Done for each Product Backlog item - the exact standard of "done" that has been communicated to the Product Owner. The team commits to completing each selected item fully to that agreed standard, not partially.

• A is wrong because Scrum doesn't prescribe equal time allocation across activities. Teams self-organize and decide how to distribute effort based on what each item actually needs.
• C is wrong because "all development work and at least some testing" implies testing can be incomplete, which violates the Definition of Done - testing must be fully completed to the agreed standard, not partially.
• D is wrong because this describes scope spillover, which Scrum discourages. If a team can't complete an item to the Definition of Done within the Sprint, it should not be split across Sprints arbitrarily - incomplete items are returned to the Product Backlog.

Memory tip: Think of it as a promise to the Product Owner - the team selects items it can fully deliver to the standard it already told the PO, no more, no less. "Done means done as defined."

No community discussion yet for this question.