How to handle confusion of "user stories" term in agile methodology?
I find myself in an non-agile environment where "user story" actually means "use case, backed by an excel requirements specification, a testing specification doc, and a few required wireframes || mock ups thrown in". They want to go agile. If the voices in the product owner's ear hear 'user stories' they'll not handle it well. "user story" has years of improper use here.I thought this would be a fast google, as I doubt I'm the first person to run into this.How should I handle non-standard use of "user-stories"?