Skip to main content

What is User Story ?

A User Story is a short description of something that your customer will do when they come to your website or use your application/software,  focused on the value or result they get from doing this thing.

User stories are:
  • written from the point of view of a person using your website or application
  • written in the language that your customers would use.


Three C’s of the user story:

Card – stories are traditionally written on note cards, and these cards can be annotated with extra details
Conversation – details behind the story come out through conversations with the Product Owner
Confirmation – acceptance tests confirm the story is finished and working as intended.


Template for User Stories :

A user story template often uses the following type of format:

As a <role>, I want <feature> so that <reason>.

Examples of user stories are:
As a user, I want to upload photos so that I can share photos with others.





Above are the examples of User Stories.

We will keep you posted for more articles on Scrum.
Kindly subscribe for more amazing articles.

Comments

Post a Comment

Popular posts from this blog

Agile Story Point Estimation Techniques - T-Shirt Sizing by - Ankur Mistry

In my previous articles, we have discussed  Agile Story Point Estimation  and  Agile Story Point Estimation Techniques - Planning Poker . In this article, we will learn Story Point Estimation using T-Shirt Size Technique. What is T-shirt sizing? T-shirt Sizing is one of the Story points sizing technique to estimate user story usually used in agile projects. It's a relative Estimation Technique. Rather than using a number of planning pokers, here, Items are classified into t-shirt sizes: XS, S, M, L, XL. The term originates from the way T-shirt sizes are indicated in the US. Rather than having T-shirts in sizes 4, 5, 6 etc, there are just a few sizes: Small (S), Medium (M), Large (L) and Extra Large (XL) and so on. With T-shirt measuring, the development team is made a request to evaluate whether they think a story is extra-small, small, medium, large, extra-large, or double extra-large. By expelling the numerical score, the development team is allow...
Post a Comment
Read more

Retrospective Meetings By:Namrata Parik

This article talks about the least important meeting in a Sprint, the retrospective meeting, at  least as considered by the business and sometimes also by the developers. It is often considered to be a waste of time and given the least priority, and sometimes even omitted if there are time constraints. In fact it is the most important meeting but does not show any immediate business value. Talking about my own experience, we were newly into the project and the geek in the team was not getting enough technical tasks to devour, resulting in not so good documentations by him and his general disinterest in the team. This was discussed in the retrospective and his problem was faced, assessed and solved within a span of two weeks (a single Sprint), and he was given enough tasks to fulfill his coding appetite, resulting in better output by the entire team. Talking about retrospective techniques, the most effective way to conduct a retrospective is the Timeline Review. The te...
Post a Comment
Read more

Scrum Framework - 5 Events in Scrum Framework - By Ankur Mistry

In my previous articles, we have discussed  3 Roles  and  3 Artifacts  in Scrum. In this article, we are going to discuss 5 events in the Scrum Framework. There are Five events in Agile Scrum Framework. Sprint Planning Daily Scrum Sprint Review Sprint Retrospective The Sprint ( Figure: Life cycle of Scrum from  http://www.agiletroop.com/product/life-cycle-of-scrum/ ) Sprint Planning  is the event in which the Product Owner presents the ordered product backlog to the development team. As the word suggests, 'Sprint Planning' means we are going to plan the work to be done in the Sprint. There are two main parts - 'What' and 'How'. 'What' can be done in this Sprint? 'How' will the selected work get done? What can be done in the Sprint - In this part, the Product Owner presents the product backlog items with high business value tasks as a first priority to the development team. All team members collaborate to understand ...
1 comment
Read more