{"id":58010,"date":"2019-11-19T09:02:01","date_gmt":"2019-11-19T17:02:01","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/devops\/?p=58010"},"modified":"2019-11-18T12:26:23","modified_gmt":"2019-11-18T20:26:23","slug":"a-sprint-burndown-widget-with-everything-youve-been-asking-for","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/devops\/a-sprint-burndown-widget-with-everything-youve-been-asking-for\/","title":{"rendered":"A Sprint Burndown widget with everything you&#8217;ve been asking for"},"content":{"rendered":"<p>With <a href=\"https:\/\/docs.microsoft.com\/en-us\/azure\/devops\/release-notes\/2019\/sprint-160-update#reporting-1\" rel=\"noopener noreferrer\" target=\"_blank\">Sprint 160<\/a>, we are releasing a new Sprint Burndown widget that lets <strong>you<\/strong> choose how to burndown for a sprint.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2019\/11\/sprint-burndown-widget.png\" alt=\"Azure DevOps Sprint Burndown widget - configured by Count of Tasks\" width=\"634\" height=\"453\" class=\"alignnone size-full wp-image-58012\" srcset=\"https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2019\/11\/sprint-burndown-widget.png 634w, https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2019\/11\/sprint-burndown-widget-300x214.png 300w\" sizes=\"(max-width: 634px) 100vw, 634px\" \/><\/p>\n<p>You can burndown by <strong>Story Points<\/strong>, <strong>count of Tasks<\/strong>, or <strong>custom fields<\/strong>. You can create a burndown for <strong>Epics<\/strong>, <strong>Features<\/strong>, and <strong>Stories<\/strong>. In fact, you can burndown by summing any field or by counting any type of work item. The new widget displays average burndown, % complete, and scope increase. You can choose to burndown on a specific team, which lets you display sprint burndowns for multiple teams on the same dashboard. With all this great information to display, we let you resize it up to 10&#215;10 on the dashboard<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2019\/11\/sprint-burndown-config-2-1.png\" alt=\"Azure DevOps Sprint Burndown widget - Configuration\" width=\"693\" height=\"961\" class=\"alignnone size-full wp-image-58040\" srcset=\"https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2019\/11\/sprint-burndown-config-2-1.png 693w, https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2019\/11\/sprint-burndown-config-2-1-216x300.png 216w\" sizes=\"(max-width: 693px) 100vw, 693px\" \/><\/p>\n<p>You&#8217;ll notice that we have two versions in the widget catalog.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2019\/11\/sprint-burndown-catalog.png\" alt=\"Azure DevOps Sprint Burndown widget - Widget Catalog\" width=\"406\" height=\"318\" class=\"alignnone size-full wp-image-58015\" srcset=\"https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2019\/11\/sprint-burndown-catalog.png 406w, https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2019\/11\/sprint-burndown-catalog-300x235.png 300w\" sizes=\"(max-width: 406px) 100vw, 406px\" \/><\/p>\n<p>The new version requires access to Analytics. Since some customers restrict <a href=\"https:\/\/docs.microsoft.com\/en-us\/azure\/devops\/report\/powerbi\/analytics-security?view=azure-devops\" rel=\"noopener noreferrer\" target=\"_blank\">&#8220;View Analytics&#8221; permissions<\/a>, we kept the legacy version as a backup option for them.<\/p>\n<p>To try the new version, you can add it from the widget catalog. Or, you can edit the configuration of an existing legacy Sprint Burndown widget and check the <strong>Try the new version now<\/strong> box.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2019\/11\/sprint-burndown-legacy-config.png\" alt=\"Azure DevOps Sprint Burndown widget - Easy upgrade to new version\" width=\"420\" height=\"330\" class=\"alignnone size-full wp-image-58016\" srcset=\"https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2019\/11\/sprint-burndown-legacy-config.png 420w, https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2019\/11\/sprint-burndown-legacy-config-300x236.png 300w\" sizes=\"(max-width: 420px) 100vw, 420px\" \/><\/p>\n<p>For more information, check out our <a href=\"https:\/\/docs.microsoft.com\/en-us\/azure\/devops\/report\/dashboards\/configure-sprint-burndown?view=azure-devops&#038;tabs=remaining-work%2Cmay#the-sprint-burndown-widget\" rel=\"noopener noreferrer\" target=\"_blank\">docs<\/a>.<\/p>\n<p>We know many of you have been <a href=\"https:\/\/developercommunity.visualstudio.com\/content\/idea\/365784\/sprint-burndown-using-story-points-effort.html\" rel=\"noopener noreferrer\" target=\"_blank\">asking for these features<\/a> for a while. We are so happy to provide them. Enjoy!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Sprint burndown the way you want. Burndown by Story Points, count of Tasks, custom fields. Create burndowns on Epics, Features, Stories. Resize to 10&#215;10.<\/p>\n","protected":false},"author":106,"featured_media":58012,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[227,250],"tags":[],"class_list":["post-58010","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-agile","category-reporting"],"acf":[],"blog_post_summary":"<p>Sprint burndown the way you want. Burndown by Story Points, count of Tasks, custom fields. Create burndowns on Epics, Features, Stories. Resize to 10&#215;10.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/58010","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/users\/106"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/comments?post=58010"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/58010\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media\/58012"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media?parent=58010"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/categories?post=58010"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/tags?post=58010"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}