The User Experience (UX) team does not believe in Agile development. They say, "We have to understand the full behavior of the eventual system in order to be able to define an effective user…

Question

Options

• AUser experience is indeed a different concept and the team should be exempt from working in
• BJust like system architecture, the entire user experience should be fully designed before an
• CSince the team is working in timeboxes, this has been proven to be the most effective way to
• DIt's important to have an overall user experience vision before implementation, but the vision can

• A
  5% (2)
• B
  14% (6)
• C
  5% (2)
• D
  76% (32)

Explanation

Option D captures the Agile balance between upfront thinking and iterative delivery: a high-level UX vision is valuable and encouraged, but that vision doesn't need to be fully specified before a single sprint begins - it can be elaborated, validated, and refined sprint by sprint as the team learns more about real user behavior.

Why the distractors fail:

• A is wrong because exempting UX from timeboxes creates a bottleneck and a two-speed team - exactly the coordination problem Agile tries to eliminate.
• B mirrors a Waterfall mindset. Agile explicitly rejects "design everything before building anything," including for architecture and UX.
• C is wrong because it dismisses the UX team's concern rather than engaging with it - and the premise ("since the team is working in timeboxes") doesn't logically address the objection raised.

Memory tip: Think of it as a "lighthouse, not a blueprint" - in Agile, UX sets a directional vision (the lighthouse) that guides each iteration, rather than a fully detailed blueprint that must be complete before construction starts.

No community discussion yet for this question.