Who writes user stories?

In early product discussions, the team talks about requirements and records them in the form of user stories. The product backlog is always valid and will never remain frozen. So if someone thinks the requirements are missing or something can add value to the customer, he can add this as a backlog user story. There are no rules or guidelines that only the product owner needs to write a story. The person who writes the story needs to understand exactly what it means and how to write it because it has a fixed format.

Writing user stories also gives team members a sense of ownership and they can easily connect when they are involved in the writing process. User stories are written throughout agile development. Storytelling workshops are usually held at the beginning of an agile project. Each member of the team contributes to the goal of creating a product backlog that completely lists the features that will be added during the course of the project.