Agile software development process utilizes
user stories as a fundamental structure of how a particular piece of software
is supposed to work and what basic functionality it has to provide to an
end-user. Krystian Kaczor (2010) defined a user story as "a short description of
customer’s need. User Stories are commonly used in agile software methodology
and frameworks such as Extreme Programming or Scrum as a way of gathering
requirements."
Most of the time user stories are written
in a similar manner as follows: As who
I want what so that why. For example: as a user I would like
to be able to export data in Microsoft Excel format so that the data could be
filtered or sorted later on. In the example above, I picked "user" as
a who would be using a product. Then I stated the functionality that as the
specified person I would've liked to have. And finally, I write down the
purpose associated with the mentioned functionality.
 |
| http://www.agiletesting.info/wp-content/uploads/2010/12/story_on-index-card.jpg |
User stories help to develop and deliver a
product that functions according to an end-user wishes. They help a developing
company or a team to estimate potential costs and time needed to finish the
product. The user stories also help to eliminate certain misunderstandings,
which may arise between developers and a client, as well as wrong assumptions.
As
for the project that I'm currently working on, the user stories are on the main
page of our project's website: https://sites.google.com/a/sjsu.edu/team-2015-spr-academic-scheduling/.
There are nine user stories listed under "User Stories:" title.
Kaczor, K. (2010, December 7). Five Common
Mistakes in Writing User Stories. Retrieved March 15, 2015, from
http://www.agiletesting.info/5-common-mistakes-in-writing-user-stories-13
No comments:
Post a Comment