During sprint planning, team members have differing opinions on a feature that delivers business value but fails to provide a long-term solution for the customer. How should the team resolve this?

Question

Options

• ARefer to the values of the agile framework and the team
• BReview the signed customer contract
• CCheck the sprint priority list
• DSubmit the problem to the product owner

• A
  79% (27)
• B
  12% (4)
• C
  6% (2)
• D
  3% (1)

Explanation

When team members disagree about a feature that delivers short-term business value but lacks a long-term solution, the right resolution path is to return to shared agile values and team agreements. Agile values - such as customer collaboration, sustainable development, and technical excellence - provide a common framework for navigating exactly these kinds of trade-off debates. It depersonalizes the disagreement and grounds it in principles the team has already committed to. Option B (signed contract) is a waterfall mindset and contrary to the agile value of customer collaboration over contract negotiation. Option C (sprint priority list) doesn't address the underlying values conflict. Option D (escalating to the product owner) is valid for prioritization decisions but not for resolving values-based team disagreements.

No community discussion yet for this question.