{"id":5713,"date":"2012-01-27T09:55:07","date_gmt":"2012-01-27T09:55:07","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/visualstudioalm\/2012\/01\/27\/team-foundation-service-preview-configure-a-master-backlog-and-sub-teams\/"},"modified":"2019-02-14T18:00:20","modified_gmt":"2019-02-15T02:00:20","slug":"team-foundation-service-preview-configure-a-master-backlog-and-sub-teams","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/devops\/team-foundation-service-preview-configure-a-master-backlog-and-sub-teams\/","title":{"rendered":"Team Foundation Service Preview \u2013 Configure a master backlog and sub-teams"},"content":{"rendered":"<h3>&nbsp;<\/p>\n<h3>One backlog to rule them all&hellip;<\/h3>\n<p>One common practice we&rsquo;ve seen our customers use is to have a master backlog, which &ldquo;feeds&rdquo; several teams. The master backlog is prioritized and maintained, and when it comes time to plan for the next sprint, all the teams gather together and &ldquo;sign up&rdquo; for backlog items to work on in the upcoming sprint.<\/p>\n<p>That way, they can ensure that all teams are working on the most important items for each sprint. <\/p>\n<p>This <a href=\"http:\/\/blogs.msdn.com\/b\/greggboer\/archive\/2012\/01\/27\/tfs-vnext-configuring-your-project-to-have-a-master-backlog-and-sub-teams.aspx\" target=\"_blank\">blog post<\/a> will tell you how to configure and use a master backlog using the Team Foundation Service Preview.<\/p>\n<\/h3>\n","protected":false},"excerpt":{"rendered":"<p>&nbsp; One backlog to rule them all&hellip; One common practice we&rsquo;ve seen our customers use is to have a master backlog, which &ldquo;feeds&rdquo; several teams. The master backlog is prioritized and maintained, and when it comes time to plan for the next sprint, all the teams gather together and &ldquo;sign up&rdquo; for backlog items to [&hellip;]<\/p>\n","protected":false},"author":77,"featured_media":45953,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[227,253,1],"tags":[],"class_list":["post-5713","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-agile","category-azure-devops-server","category-devops"],"acf":[],"blog_post_summary":"<p>&nbsp; One backlog to rule them all&hellip; One common practice we&rsquo;ve seen our customers use is to have a master backlog, which &ldquo;feeds&rdquo; several teams. The master backlog is prioritized and maintained, and when it comes time to plan for the next sprint, all the teams gather together and &ldquo;sign up&rdquo; for backlog items to [&hellip;]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/5713","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\/77"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/comments?post=5713"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/5713\/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=5713"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/categories?post=5713"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/tags?post=5713"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}