> User stories as requirements seems to be the dominant understanding. Really? Maybe I'm just lucky but I've not seen it yet in my career (10 years). The "as

> User stories as requirements seems to be the dominant understanding. Really? Maybe I'm just lucky but I've not seen it yet in my career (10 years). The "as a, I want, so that" text is normally just a summary of who/what/why, and the ticket will include acceptance criteria detailing the changes to be implemented. For features larger than a couple of tickets PO's and PM's will usually keep up with requirements in planning docs that are in Confluence, Google Docs, etc.