Shared understanding means that a team holds the same interpretation of a story’s requirements and expected behavior. Teams build it by exploring concrete examples together, clarifying assumptions, and using consistent business-domain terms. The result may change the story itself, sometimes substantially. section 1.3.2 section 6.1
Consider a delivery-address change:
- If the order is still being prepared, the change is accepted; if it has been collected, the change is rejected. Discussing these cases can reveal further questions, such as what feedback the customer receives or what happens when the new address is outside the delivery area. section 1.3.2
- When developers and testers work out requirements independently, their separate interpretations can lead to disputes over whether a difference is a bug or a feature. Collaborative discussion reduces this risk. section 5.3.9
Discovery uses examples to learn what behavior is wanted; formulation later records that understanding in clear, domain-based language so people who were not present can interpret it consistently. Keep discovery focused on learning requirements: exploring every test combination belongs outside that conversation. Recorded examples can later serve as test cases. section 9.2.1 section 3.4



