Just a quick feedback on this: several people I respect find that this works really well. I've had mixed success. For example I often find people writing thin

Just a quick feedback on this: several people I respect find that this works really well. I've had mixed success. For example I often find people writing things like "As a user, I want to ensure that the application never crashes, so that I never lose data". This is not specific enough and fails the "how do I know when I'm done" test. I usually prefer to list the acceptance criteria in a format similar to "When <user role> does <X>, <Y> will happen". I should be able to use the application in the <user role>, do <X> and observe that <Y> does not happen. That's my kind of litmus test. The <business value> is super important in the story, but I don't like them in acceptance criteria because they are often too high level. This, in turn, forces the acceptance criteria to a higher level in order to match. But like I said, some people I respect highly really like this format, so it's possible that I'm missing something.