What should a Development Team do if they don't understand a functional requirement?

Question

Options

• ARequest a specialist to be added to the Development Team.
• BMove the item to a future Sprint.
• CComplete as much as possible and add the remaining work as a new Product Backlog item.
• DWork with the Product Owner to determine what is possible and acceptable.

• A
  5% (1)
• B
  5% (1)
• D
  91% (20)

Explanation

When a Development Team doesn't understand a functional requirement, collaborating with the Product Owner (D) is the correct Scrum practice - the Product Owner is the authority on what the product should do and why, making them the right person to clarify intent, negotiate scope, or redefine acceptance criteria so the team can move forward confidently within the Sprint.

Why the distractors fail:

• (A) Adding a specialist is a structural team change that bypasses the immediate problem - a knowledge gap doesn't necessarily require a new team member, especially when the Product Owner can clarify.
• (B) Moving the item to a future Sprint avoids the problem rather than solving it; deferral without understanding is just postponed confusion.
• (C) Delivering partial work and creating a new backlog item fragments the requirement and produces potentially unusable increments - Scrum values delivering "Done" increments, not half-finished work.

Memory tip: In Scrum, when in doubt, talk to the Product Owner - they own the "what" and "why," while the team owns the "how." If you're ever unsure on an exam who to consult about requirements, the PO is almost always the answer.

No community discussion yet for this question.