title: In scrum, is changing acceptance criteria during a sprint OK?
body: <p>My organization is currently implementing Scrum.  While working on a product backlog item to change the way some business logic is processed, we realized that some of the business logic is flawed.  The PBI and its acceptance criteria are currently oriented towards modifying the implementation of the existing business logic.  The PO feels this change to the business logic itself is a high priority and should be worked into the sprint somehow, and the dev team agrees, especially since it would make a lot of sense to do both things together, from a development standpoint.  </p>
  
  <p>We are unsure, however, if it would make more sense to modify the acceptance criteria or create a new PBI and pull it into the sprint right away.  I personally lean towards a new PBI because I feel like this is a separate story and set of acceptance criteria from the original PBI, and I'm skeptical about changing acceptance criteria mid-sprint in general.  The PO pointed out that both this new requirement and the original PBI will be implemented at the same time, and the original PBI is pointless without the new requirements to be addressed.  So the PO feels it would be more appropriate to adjust the acceptance criteria of the original PBI instead of creating two separate ones that reflect the same implementation in the end.</p>
  
  <p>Is one of these approaches more scrum-appropriate than the other?</p>