A user story is a feature request (or need) expressed from the point of view of a user with a description of the value it provides to that user.
The Daily Scrum was meant for Developers to give each other an idea of the work they had done the day before and their plans for the day in progress. It was never meant for Product Managers or Product Owners to be part of them unless they are taking part of the work in the actual product by working on Sprint Backlog Items.
The final users are the most important part of the information system because if the system does not solve their problems or does not do what they expect, they won’t use it. There is where we see the resistance to change from users when they don’t feel part of the information system planning, and when they feel that all decisions were made without considering their points of view.
If the requirements are not clear or unknown at first, an agile approach will help the team understand the needs of the users while delivering incremental updates and gathering feedback from the market.