On an agile project, some of the development team is struggling to understand how the tasks and user stories fit into the overall product. How should this be addressed?

Question

Options

• AReview the iteration goals and have the team each describe the work to create shared
• BCreate a story map for the minimal viable product (MVP) functionality
• CCapture this as a task in the retrospective and ensure there is more detail provided at the next
• DHave the product owner explain the product vision and review the release plan with the team

• A
  3% (2)
• B
  77% (47)
• C
  15% (9)
• D
  5% (3)

Explanation

A story map is a visual technique that organizes user stories across two dimensions: the user journey (horizontal) and priority/detail levels (vertical). It gives the entire team a shared view of how individual stories and tasks contribute to the overall product experience. This directly addresses the problem of team members not seeing the big picture. Retrospective action items (option C) delay resolution, and the product vision review (option D) is high-level but less actionable than the concrete visual structure a story map provides.

No community discussion yet for this question.