## Why Is It Acceptable to Abandon a Product Goal? Scrum values learning over blind adherence to plans. The commitment is to transparency and focus, not to sticking with outdated decisions. When new information arises, abandoning or reformulating the Product Goal is a natural consequence of empiricism. >[!metaphor] >Sticking to an outdated Product Goal is like continuing to drive to Aunt Effie’s house even after you get the call that she’s passed away. The original plan made sense when you left, but the purpose behind it no longer exists. Product Goals should guide decisions, not trap you into finishing a trip that no longer matters. ## Works Consulted 1. [[Prompted to Learn]] Study Session | Explored 22 Jul. 2025 | Define the purpose of a Product Goal in Scrum. 2. [Product Goal](https://www.scrum.org/resources/product-goal) | Scrum.org | Accessed 23 Jul. 2025. ## Connections follows:: [[1.3d A Product Goal Must Evolve When Invalidated]] topics:: [[Product Goal]], [[Empiricism]], [[Plan Adherence]] ![[Footer]]