{"id":38552,"date":"2016-11-23T19:26:13","date_gmt":"2016-11-24T01:26:13","guid":{"rendered":"http:\/\/talkaboutsoftware.wordpress.com\/?p=280"},"modified":"2016-11-23T19:26:13","modified_gmt":"2016-11-24T01:26:13","slug":"user-stories","status":"publish","type":"post","link":"https:\/\/kenscourses.com\/tc1019fall2016\/syndicated\/user-stories\/","title":{"rendered":"User Stories"},"content":{"rendered":"<p>User sotries are one of the primary development artifacts for Scrum and Extreme Programming (XP) project teams. A user story is a very high-level definition of a requirement, containing just enough information so that the developers can produce a reasonable estimate of the effort to implement it. This article covers the following topics:<\/p>\n<p>A <b>user story<\/b> is a tool used in Agile software development to capture a description of a software feature from an end-<b>user<\/b> perspective. The <b>user story<\/b>describes the type of <b>user<\/b>, what they want and why. A <b>user story<\/b> helps to create a simplified description of a requirement.<\/p>\n<p>&nbsp;<\/p>\n<p>How to create a good user story?<\/p>\n<p>1.-Users Come First<\/p>\n<p>2.-Use Personas to Discover the Right Stories<\/p>\n<p>3.- Create\u00a0Stories Collaboratively<\/p>\n<p><img class=\"alignnone size-full wp-image-290\" src=\"https:\/\/talkaboutsoftware.files.wordpress.com\/2016\/11\/drgrd.png?w=736\" alt=\"drgrd\" srcset=\"https:\/\/talkaboutsoftware.files.wordpress.com\/2016\/11\/drgrd.png 310w, https:\/\/talkaboutsoftware.files.wordpress.com\/2016\/11\/drgrd.png?w=150 150w, https:\/\/talkaboutsoftware.files.wordpress.com\/2016\/11\/drgrd.png?w=300 300w\" sizes=\"(max-width: 310px) 100vw, 310px\"   \/><\/p>\n<p>4.-Keep your Stories Simple and Concise<\/p>\n<p>5.-Start with Epics<\/p>\n<p>6.-Refine\u00a0the Stories\u00a0until They are Ready<\/p>\n<p>7.-Add Acceptance Criteria<\/p>\n<p>8.-Use Paper Cards<\/p>\n<p>9.-Keep your Stories Visible and Accessible<\/p>\n<p>10.-Don\u2019t Solely Rely on User Stories<img class=\"alignnone size-full wp-image-291\" src=\"https:\/\/talkaboutsoftware.files.wordpress.com\/2016\/11\/rgdrgdf.jpg?w=736\" alt=\"rgdrgdf\" srcset=\"https:\/\/talkaboutsoftware.files.wordpress.com\/2016\/11\/rgdrgdf.jpg 600w, https:\/\/talkaboutsoftware.files.wordpress.com\/2016\/11\/rgdrgdf.jpg?w=150 150w, https:\/\/talkaboutsoftware.files.wordpress.com\/2016\/11\/rgdrgdf.jpg?w=300 300w\" sizes=\"(max-width: 600px) 100vw, 600px\"   \/><\/p><br \/>  <a rel=\"nofollow\" href=\"http:\/\/feeds.wordpress.com\/1.0\/gocomments\/talkaboutsoftware.wordpress.com\/280\/\"><img alt=\"\" border=\"0\" src=\"http:\/\/feeds.wordpress.com\/1.0\/comments\/talkaboutsoftware.wordpress.com\/280\/\" \/><\/a> <img alt=\"\" border=\"0\" src=\"https:\/\/pixel.wp.com\/b.gif?host=talkaboutsoftware.wordpress.com&#038;blog=115272766&%23038;post=280&%23038;subd=talkaboutsoftware&%23038;ref=&%23038;feed=1\" width=\"1\" height=\"1\" \/>","protected":false},"excerpt":{"rendered":"<p>User sotries are one of the primary development artifacts for Scrum and Extreme Programming (XP) project teams. A user story is a very high-level definition of a requirement, containing just enough information so that the developers can produce a reasonable estimate of the effort to implement it. This article covers the following topics: A user &hellip; <a href=\"https:\/\/kenscourses.com\/tc1019fall2016\/syndicated\/user-stories\/\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">User Stories<\/span><\/a><\/p>\n","protected":false},"author":34,"featured_media":290,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5,4],"tags":[46],"class_list":["post-38552","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blogs","category-syndicated","tag-uncategorized"],"_links":{"self":[{"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/posts\/38552","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/users\/34"}],"replies":[{"embeddable":true,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/comments?post=38552"}],"version-history":[{"count":2,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/posts\/38552\/revisions"}],"predecessor-version":[{"id":38781,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/posts\/38552\/revisions\/38781"}],"wp:attachment":[{"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/media?parent=38552"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/categories?post=38552"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/tags?post=38552"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}