gaspersic/freeCodeCamp
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Update index.md (#29918)

Browse Source 
Added information on how user stories are usually recorded
This commit is contained in:
Parul
2019-01-14 20:06:23 -05:00
committed by Tom
parent cc0e2163fb
commit 8c4959b34a
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
guide/english/agile/user-stories/index.md
View File

@ -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.