After 30 plus years doing requirements for systems projects I am now with an organization that wants to adopt user stories., as directed by a new manager of the PMO. I have used a lot of different methods/techniques over the years, so I am not averse to something new (to me , anyway).
My question about user stories has always been about creating the initial backlog: how do you know you haven't missed something important? Something that would have changed how the development would have gone if you knew it sooner than later? It is about the scope of requirements, and getting a complete set of stories.
I recognize there are some kinds of systems where this is not an issue, where you are truly developing a new product and the first set of features is what the PO wants. There are other types, however, where incomplete scope is an issue, like compliance projects or process automation.
So, my question is: for anyone who adopted user stories, how did it go? Any issues about scope definition?