{"id":12033,"date":"2013-10-30T15:48:51","date_gmt":"2013-10-30T13:48:51","guid":{"rendered":"https:\/\/mozaicworks.com\/?p=5937"},"modified":"2013-10-30T15:48:51","modified_gmt":"2013-10-30T13:48:51","slug":"what-do-the-user-stories-mean","status":"publish","type":"post","link":"https:\/\/mozaicworks.com\/blog\/what-do-the-user-stories-mean","title":{"rendered":"What do the User Stories mean?"},"content":{"rendered":"

\u00a0User Stories are the bridge between the customer and the development team. They are short, clear, written sentences which tell everyone what the system needs to do for the user.<\/span><\/em><\/p>\n

For the Agile practitioners, the user stories are known as one of the\u00a0primary development artifacts for Scrum project teams. Those artifacts resume clearly the requirements so that the development team can do the appropriate estimation of the time and effort to implement it.<\/p>\n

Example of user story from Wikipedia<\/a>:
\n\u00a0 \u00a0 \u00a0 \u00a0As a\u00a0<\/strong>user closing the application,
\n\u00a0 \u00a0 \u00a0 \u00a0I want\u00a0<\/strong>to be prompted to save anything that has changed since the last save
\n\u00a0 \u00a0 \u00a0 \u00a0so that\u00a0<\/strong>I can preserve useful work and discard erroneous work.
\nEstimate:7
\nPriority:4<\/p>\n

Written by the customers, the user stories<\/strong> have the followings characteristics<\/strong>:<\/p>\n