{"id":36015,"date":"2017-09-25T08:00:00","date_gmt":"2017-09-25T08:00:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/devops\/?p=36015"},"modified":"2019-02-14T15:51:09","modified_gmt":"2019-02-14T23:51:09","slug":"burndown-and-burnup-widgets-available-for-the-vsts-analytics-extension","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/devops\/burndown-and-burnup-widgets-available-for-the-vsts-analytics-extension\/","title":{"rendered":"Burndown and Burnup Widgets available for the VSTS Analytics Extension"},"content":{"rendered":"<p>UPDATE 10\/06\/2017. The S123 Deployment is complete. The Burndown \/ Burnup widgets are now available for all accounts.<\/p>\n<p>===<\/p>\n<p>The Burndown and Burnup Widgets are <a href=\"https:\/\/docs.microsoft.com\/en-us\/vsts\/release-notes\/2017\/sep-15-team-services#burndown-and-burnup-widgets\">now available<\/a> for those who have installed the <a href=\"https:\/\/marketplace.visualstudio.com\/items?itemName=ms.vss-analytics\">Analytics Extension<\/a> on their Visual Studio Team Services (VSTS) accounts. <del>(<strong>NOTE<\/strong>: The <a href=\"https:\/\/docs.microsoft.com\/en-us\/vsts\/release-notes\/2017\/sep-15-team-services\">S123 Deployment <\/a>should be completed by the end of September. If the widget is not available on your account, check back later)<\/del><\/p>\n<p><span><span>The <strong>Burndown widget<\/strong> lets you display a burndown across multiple teams and multiple sprints. You can use it to create a release burndown, a bug burndown, or a burndown on just about any scope of work over any time period. You can even create a burndown that spans team projects!<\/span><\/span><span><span>\n<\/span><\/span><\/p>\n<div>The <strong>Burndown widget<\/strong> helps you answer the question: <b>Will we complete this project on time? <\/b><\/div>\n<div><b>\u00a0<\/b><\/div>\n<div>To help you answer that question, it provides these features:<\/div>\n<ul>\n<li>Displays percentage complete<\/li>\n<li>Computes average burndown<\/li>\n<li>Shows you when you have items not estimated with story points<\/li>\n<li>Tracks your scope increase over the course of the project<\/li>\n<li>Projects your project&#8217;s completion date based on historical burndown and scope increase<\/li>\n<\/ul>\n<div>You can burndown on any work item type based on count of work items or by the sum of a specific field (e.g.: Story Points). You can burndown using daily\/weekly\/monthly intervals or based on an iteration schedule. You can even add additional filter criteria to fine tune the exact scope of work you are burning down.<\/div>\n<p><span><span><\/span><\/span><\/p>\n<div>\n<div>The widget is highly configurable allowing you use it for a wide variety of scenarios. We expect you will find amazing ways to use these two widgets.<\/div>\n<p>&nbsp;<\/p>\n<p><span><span>Example of a Release Burndown over Sprints <\/span><\/span><span><span><img decoding=\"async\" width=\"695\" height=\"498\" class=\"alignnone wp-image-36425 size-full\" alt=\"\" src=\"https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2017\/09\/burndownup-release-burndown2.png\" \/><\/span><\/span><\/p>\n<p><span>Example of a Bug Burndown over Days<\/span><span><span><img decoding=\"async\" width=\"700\" height=\"518\" class=\"alignnone wp-image-36306 size-full\" alt=\"\" src=\"https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2017\/09\/burndownup-bug-burndown.png\" \/> <\/span><\/span><\/p>\n<\/div>\n<div><span><span>The <strong>Burnup widget<\/strong> is just like the Burndown widget, except that it plots the work you have completed, rather than the work you have remaining.\u00a0<\/span><\/span><\/div>\n<div><\/div>\n<p>Example of Stories Burnup over Weeks<img decoding=\"async\" width=\"700\" height=\"511\" class=\"alignnone wp-image-36296 size-full\" alt=\"\" src=\"https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2017\/09\/burndownup-stories-burnup.png\" \/><b><\/b><i><\/i><u><\/u><sub><\/sub><sup><\/sup><span style=\"text-decoration: line-through\"><\/span><\/p>\n<div>For more information on how to configure these powerful widgets, see <a href=\"https:\/\/docs.microsoft.com\/en-us\/vsts\/report\/guidance\/configure-burndown-burnup-widgets\">our documentation<\/a>.<\/div>\n<div><\/div>\n<div>\n<p>If you haven&#8217;t already, install <a href=\"https:\/\/marketplace.visualstudio.com\/items?itemName=ms.vss-analytics\">the Analytics Extension<\/a> to get access to the Burndown and Burnup Widgets, as well as widgets for Velocity, Lead Time, Cycle Time, and a Cumulative Flow Diagram.<\/p>\n<p>Enjoy!<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>UPDATE 10\/06\/2017. The S123 Deployment is complete. The Burndown \/ Burnup widgets are now available for all accounts. === The Burndown and Burnup Widgets are now available for those who have installed the Analytics Extension on their Visual Studio Team Services (VSTS) accounts. (NOTE: The S123 Deployment should be completed by the end of September. [&hellip;]<\/p>\n","protected":false},"author":106,"featured_media":45953,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[227,1,250],"tags":[],"class_list":["post-36015","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-agile","category-devops","category-reporting"],"acf":[],"blog_post_summary":"<p>UPDATE 10\/06\/2017. The S123 Deployment is complete. The Burndown \/ Burnup widgets are now available for all accounts. === The Burndown and Burnup Widgets are now available for those who have installed the Analytics Extension on their Visual Studio Team Services (VSTS) accounts. (NOTE: The S123 Deployment should be completed by the end of September. [&hellip;]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/36015","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=36015"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/36015\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media\/45953"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media?parent=36015"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/categories?post=36015"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/tags?post=36015"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}