During sprint planning the product owner wants the team to prioritize and deliver a number of features which have the highest business value. Due to technical dependencies, the team does not agree…

Question

Options

• AEncourage the product owner and team to reprioritize the features and select ones which can be
• BEncourage the team to continue with the current plan, do what they can, and carry forward the
• CEnsure the team captures the technical dependencies as issues within the backlog and prioritize
• DEnsure that the required subject matter experts (SMEs) are engaged by the product owner to help

• A
  6% (3)
• B
  2% (1)
• C
  85% (45)
• D
  8% (4)

Explanation

In agile, the product backlog is the single source of truth for all work, including technical constraints. When technical dependencies conflict with business prioritization, the correct action is to make those dependencies visible by capturing them as backlog items. This allows the product owner to make informed prioritization decisions with full transparency into technical risks. Reprioritizing without capturing dependencies (A) loses the technical context; pushing through the current plan (B) ignores legitimate technical risk; bringing in SMEs (D) doesn't resolve the root issue of undocumented dependencies. Capturing and prioritizing technical dependencies preserves both business value goals and technical integrity.

No community discussion yet for this question.