{"id":10661,"date":"2006-02-22T07:29:00","date_gmt":"2006-02-22T07:29:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/bharry\/2006\/02\/22\/team-foundation-server-and-the-future\/"},"modified":"2018-08-14T00:35:06","modified_gmt":"2018-08-14T00:35:06","slug":"team-foundation-server-and-the-future","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/bharry\/team-foundation-server-and-the-future\/","title":{"rendered":"Team Foundation Server and the Future"},"content":{"rendered":"<p>As you can tell from the cadence of releases and information coming out, TFS 2005 is getting pretty close to shipping.&nbsp; We&#8217;ve entered what we call &#8220;escrow&#8221;.&nbsp; That means we&nbsp;think we&#8217;ve fixed everything we need to fix and are performing our final full test pass to ensure that there haven&#8217;t been any new bugs introduced recently or any critical things we have missed.\nWith V1 now mostly behind us we&#8217;re starting to look ahead to what comes next.&nbsp; We&#8217;re collecting the lists of everything we wished we had been able to V1 and&nbsp;all of the suggestions that we&#8217;ve gotten from customers &#8211; forums, email, MSDN Product Feedback Center, etc.&nbsp; We&#8217;re also taking a high level look at what&nbsp;the core value proposition(s) for&nbsp;our next release should be and what timeframe we should be targeting.&nbsp; In V1 our core value proposition was integration.&nbsp; We set out to build, from the ground up, a set of lifecycle tools that are well integrated &#8211; thus enabling people from many different roles to work together and have access to a broad array of information that is indexed and corrolated to allow better communication among the team and management and more predictabilty for the schedule.\nWhat next?&nbsp; There are many questions we need to answer and we want your input.\n<strong>Scenario\/value proposition<\/strong> &#8211; What should be fundementally be trying to be the best at?&nbsp; Clearly our commitment to being the best and most integrated lifecycle tool set isn&#8217;t going away &#8211; but what else?&nbsp; What are the biggest challenges you face?&nbsp; Is it distributed development?&nbsp; Project\/dependency management?&nbsp; Connecting development to operations?&nbsp; Something else?\n<strong>Features<\/strong> &#8211; What features are we missing that you really wish we had.&nbsp; What could we add that would enable to to do your work faster and work better together with the people around you?&nbsp; Should we focus on performance and scale or more on ease of use?\n<strong>Timeframe<\/strong> &#8211; When do you want another release?&nbsp; No, next week isn&#8217;t an answer \ud83d\ude42&nbsp; What I&#8217;m really asking is this &#8211; do you want a short product cycle with a few targeted features or a longer product cycle with a larger increment to the value?&nbsp; What are your thoughts on how we should balance this for the next release?\n<strong>Anything else<\/strong> &#8211; Is there anything else you think we should be doing&nbsp;the next release?\nWe value your input very much.&nbsp; We want to incorporate it at the very beginning of our planning.&nbsp; Please feel free to respond in whatever way works best for you.&nbsp; Respond to this blog post.&nbsp; Send me email at <a href=\"http:\/\/blogs.msdn.commailto:bharry@microsoft.com\">bharry@microsoft.com<\/a>.&nbsp; Post on the Team Foundation Server forum on <a href=\"http:\/\/forums.microsoft.com\">http:\/\/forums.microsoft.com<\/a>.&nbsp; Whatever works for you.&nbsp; I&#8217;m eager to hear what you think.\nThank you,<\/p>\n<p>Brian<\/p>\n","protected":false},"excerpt":{"rendered":"<p>As you can tell from the cadence of releases and information coming out, TFS 2005 is getting pretty close to shipping.&nbsp; We&#8217;ve entered what we call &#8220;escrow&#8221;.&nbsp; That means we&nbsp;think we&#8217;ve fixed everything we need to fix and are performing our final full test pass to ensure that there haven&#8217;t been any new bugs introduced [&hellip;]<\/p>\n","protected":false},"author":244,"featured_media":14617,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-10661","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"acf":[],"blog_post_summary":"<p>As you can tell from the cadence of releases and information coming out, TFS 2005 is getting pretty close to shipping.&nbsp; We&#8217;ve entered what we call &#8220;escrow&#8221;.&nbsp; That means we&nbsp;think we&#8217;ve fixed everything we need to fix and are performing our final full test pass to ensure that there haven&#8217;t been any new bugs introduced [&hellip;]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/posts\/10661","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/users\/244"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/comments?post=10661"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/posts\/10661\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/media\/14617"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/media?parent=10661"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/categories?post=10661"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/tags?post=10661"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}