Planning User Stories: Creating user stories

User Stories In planning a project, Agile throws out the traditional project requirements. It instead uses a set of user stories. A user story contains short and simple descriptions of a feature from the user's perspective. The purpose for user stories is to strive towards finding value in the product. By writing down user stories, an agile team will be able to  get a better sense of product functionality.

Before user stories can be written, the product owner must have already created user roles that have the bundle experiences expected for the project. Once user roles are properly defined, user stories can be used as a conversation vehicle for requirements. When creating user stories, many tend to write them on sticky notes but a more effective way is by using a 3 x 5 index card. There are many other ways to create user stories such as using spreadsheets, but however it is decided be sure to think about the three Cs. Card, conversation, and confirmation are the standard way of properly writing down user stories.

To Further explain how user stories are constructed, a user story is only about the what and the way and not how something will work. The how is normally left up to the developers where they make the technical decisions. Upon creating a user story, it is necessary to attach a value to them. This value acts as a determining factor to importance for the final product. When values are attached, it is much easier for the product owner to understand and prioritize. It is also important to make sure that every story starts with, as a user role and then end the story with a value goal.

The last part in writing a user story is to include an acceptance criteria. The acceptance criteria confirms that everybody is aware on how to deliver the story. The acceptance criteria should closely match the user story as it is the result of the conversation with the developers. Typically the acceptance criteria is written on the back of the card. Once the acceptance criteria is written, the user story is considered as completed.

Work Cited

"Agile at Work: Planning with Agile User Stories" Lynda.com - from LinkedIn, https://www.lynda.com/Business-Skills-tutorials/Starting-user-roles/175074/387212-4.html Accessed 10 Nov. 2017.

Image provided by

www.testingexcellence.com/wp-content/uploads/2016/05/User_Story.jpg