From 8c4959b34a6edbe4a23932b2c46283820cfdccdc Mon Sep 17 00:00:00 2001 From: Parul Date: Mon, 14 Jan 2019 20:06:23 -0500 Subject: [PATCH] Update index.md (#29918) Added information on how user stories are usually recorded --- guide/english/agile/user-stories/index.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/guide/english/agile/user-stories/index.md b/guide/english/agile/user-stories/index.md index 4d5114c972..626c9c08fa 100644 --- a/guide/english/agile/user-stories/index.md +++ b/guide/english/agile/user-stories/index.md @@ -10,6 +10,8 @@ User stories should be written in non-technical terms from the perspective of th One common mistake that is made when writing user stories is writing from the perspective of the developer or the solution. Be sure to state the goal and the stakeholder need, and the functional requirements come later. +User stories are often written on sticky notes and put on walls where they are visible to the entire team. Alternatively, they can also be captured using story mapping or project management tools, such as StoriesOnBoard or JIRA. + #### Sizing a User Story: Epics and Smaller Stories An epic is a big, coarse-grained story. It is typically broken into several user stories over time—leveraging the user feedback on early prototypes and product increments. You can think of it as a headline and a placeholder for more detailed stories.