User Stories


User Stories are an Agile term for what traditionally have been called “software requirements“. They are a brief statements of the intent or need that the system must do for a particular users.
Here is the basic formula of writing a user story:

As a <role> I want <feature> so that <benefit>.

They became a good method express requirements regardless of what methodology you are using. They are good for scrum teams or for the team which uses lean methodology.

With user stories you don’t need to deal with large specifications. The intention is to response faster without overhead changing real world requirements.

User stories examples:

As a traveler, I want to reserve a hotel room.
As a vacation planner, I want to see pictures of the hotels.
As a user with a reservation, I want to cancel my reservation.
etc…

Of course for business analyst is important to ask more questions to each user story and divide it to smaller sub-stories. For example:

As a user with a reservation, I want to cancel my reservation.
– Does the user get full or partial refund?
– How far ahead must the reservation be cancelled?
– How confirmation is provided to the user?

As a result you will get such sub-stories:

As a premium member, I want to cancel at the last minute with no penalty so that I get a full refund.
As a non-premium member, I want cancel up to 24 hours so that I get a 50% refund.
As a site member, I want an email confirmation of my cancelled reservation so that I can have a record of the transaction.

After user stories are done, they should be transmitted to story points.

Source

Related Post

Definition of DONE in Software Developent Let’s imagine, that at the end of every iteration in SCRUM or any other Agile Software Development method, the developer is coming to you and saying: "I'm done with this functionality!" But you of course ask: "What do you mean done? Are you done or...
9 main Agile software development Methodologies Agile Modeling Set of concepts, principles and techniques (practices) that enables you to quickly and easily perform design and documentation for software development projects. Does not include detailed instructions on designing, contains descript...
Who is actually the Scrum Master? The Scrum Master helps the team to be productive and use they creativity in order to deliver done, working software. The main point here is that the Scrum master leads the team, but not command the team The Scrum Master is a Coach. He is not a ...
Story Points in estimating work One of effective way to estimate the work in software development is to use Story points. The story points are based on size and complexity, not duration.  They are also become unitless, they not measured by time or another units. One other good ...