Which statement describes the information within a Story?

Question

Options

• AA Story provides just enough information for the intent to be understood by both business and
• BA Story is written in full detailed specifications so that the work is ready to be implemented
• CNo further conversation is required after the Story is identified because it contains all necessary
• DStory acceptance criteria must be finalized before beginning Iteration Planning

• A
  92% (23)
• B
  4% (1)
• C
  4% (1)

Explanation

A Story is intentionally lightweight - it contains just enough information for both business stakeholders and developers to understand the intent, with the expectation that conversations will flesh out the details during implementation. Option B is wrong because Stories are not full detailed specifications; that level of detail belongs in technical design documents and defeats the purpose of iterative collaboration. Option C is wrong because Stories are meant to start conversations, not end them - the phrase "card, conversation, confirmation" (the 3 Cs of user stories) captures this: the card is just a placeholder for a conversation. Option D is wrong because acceptance criteria can be refined during Iteration Planning itself; requiring them to be finalized before planning is too rigid and contradicts Agile's embrace of evolving detail.

Memory tip: Think of a Story as a "conversation starter," not a "contract." The goal is shared understanding, not exhaustive documentation.

No community discussion yet for this question.