A while back, I wrote about using acceptance criteria as the sole definition of scope for a software product. I wanted to expand on how that helps development teams.
It gives developers a clear-cut way of ensuring that all the code they write services some business goal. If you can get rid of it and still clear all your acceptance criteria, you don't need it.
It actually makes writing requirements easier, too, once you get used to it. There's only one way to explain what you want and only one place to look to see what you already have.
