A user story is a casual, generic explanation of a software feature written from the end user's perspective. Its goal is to communicate how a software feature will benefit the customer. Putting people first is a critical component of agile software development, and a user story does just that by putting end-users at the heart of the discussion. The development team and their efforts are described in these anecdotes using non-technical language. The team knows why they're DEVELOPING, what they're building, and what value it adds after reading a user story.
Following are the advantages of using User Story:-

• The main advantage of User Story is the user-centric definition. This is because, in the end, the user will be the one who uses the PRODUCT in the relevant user scenarios. It establishes a LINK between end-users and team members.
• The User Story's syntax ensures that the objective, benefit, or value that the user wishes to attain is captured.
• The Scrum Team will benefit from the acceptance criteria because they are included in the user story.
• It is possible to make changes to a user story throughout the project's execution. If the user story's scope grows too LARGE, it must be divided into smaller user stories. The acceptance criterion's CONDITIONS can also be changed.