So Who Writes a User Story?
Since Scrum Masters should be knowledgeable in all things dealing with the scrum processes, they can be good at limiting the scope of a user story so that it doesn’t include too much for the development team to handle. Therefore, a collaborative method is best for creating good user stories.
How Do You Create a Good User Story?
Writing user stories is often not hard. However, writing good user stories can be. User stories should tell a story and should help facilitate the development of the product without being too complex or simple. Taken together, they create the product backlog which serves as the requirement document needed for the project.
A good user story should INVEST:
Independent. A good user story should be independent of other user stories. The more independent user stories are from one another, the better and easier it is to change things down the line. While this is not always possible, often splitting or combining them will solve the problem.
Negotiable. This means that the user story should allow for some discussion later. Things should be able to be negotiable and flexible in nature. Putting in too much detail at the onset will make discussion harder later on.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: