{"id":8462,"date":"2022-01-11T23:21:22","date_gmt":"2022-01-12T04:21:22","guid":{"rendered":"https:\/\/www.rushworth.us\/lisa\/?p=8462"},"modified":"2022-01-12T23:23:03","modified_gmt":"2022-01-13T04:23:03","slug":"azure-devops-features-user-stories-and-story-points","status":"publish","type":"post","link":"https:\/\/www.rushworth.us\/lisa\/?p=8462","title":{"rendered":"Azure DevOps \u2013 Features, User Stories, and Story Points"},"content":{"rendered":"<p>I had wanted to classify my ADO work items as \u201cfeatures\u201d (i.e. something someone asked to be added to an application), \u201cbugs\u201d (i.e. some intended functionality that was not working as designed). <em>Bugs<\/em> have a story point field, but <em>features<\/em> do not appear to have their own story point field. They, instead, are a roll-up of the story points of their subordinate user stories. Which makes sense <em>except<\/em> that I\u2019ve now got to have two work items for every feature. Rolling up larger requests into sprint-sized work units is how we use <em>epics<\/em>. So I\u2019ve instead found myself with user stories tagged with \u201cfeatures\u201d that fall into epics (or <em>don\u2019t<\/em> in the case of a small feature request).<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" width=\"812\" height=\"337\" class=\"wp-image-8463\" src=\"https:\/\/www.rushworth.us\/lisa\/wp-content\/uploads\/2022\/01\/word-image.png\" srcset=\"https:\/\/www.rushworth.us\/lisa\/wp-content\/uploads\/2022\/01\/word-image.png 812w, https:\/\/www.rushworth.us\/lisa\/wp-content\/uploads\/2022\/01\/word-image-300x125.png 300w, https:\/\/www.rushworth.us\/lisa\/wp-content\/uploads\/2022\/01\/word-image-768x319.png 768w, https:\/\/www.rushworth.us\/lisa\/wp-content\/uploads\/2022\/01\/word-image-750x311.png 750w\" sizes=\"auto, (max-width: 812px) 100vw, 812px\" \/><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I had wanted to classify my ADO work items as \u201cfeatures\u201d (i.e. something someone asked to be added to an application), \u201cbugs\u201d (i.e. some intended functionality that was not working as designed). Bugs have a story point field, but features do not appear to have their own story point field. They, instead, are a roll-up &hellip;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1510],"tags":[1091,1092],"class_list":["post-8462","post","type-post","status-publish","format-standard","hentry","category-ado","tag-ado","tag-azure-devops"],"_links":{"self":[{"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=\/wp\/v2\/posts\/8462","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=8462"}],"version-history":[{"count":1,"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=\/wp\/v2\/posts\/8462\/revisions"}],"predecessor-version":[{"id":8464,"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=\/wp\/v2\/posts\/8462\/revisions\/8464"}],"wp:attachment":[{"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=8462"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=8462"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=8462"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}