title: How is TFS 2010 used within Microsoft for scrum sprinting?
body: <p>We are a Microsoft shop, and so using other incompatible tools for Scrum does not make as much sense. So, we use <code>TFS</code> - for Scrum as well.</p>
  
  <p>However, we found <code>TFS</code> templates to be rather simplistic. There is no way that <code>MSFT</code> can release the next Visual Studio, or the next .Net framework by doing all of the planning using TFS tasks.</p>
  
  <p>What is Microsoft hiding from the rest of the world?
  Alternatively, how do you use TFS 2010 for scrum in enterprise (=huge size) software?</p>
  
  <p><strong><em>EDIT:</em></strong> Specifically, trying to figure out how different pieces fit together can be hard. Imagine the following epic (as if it was developed in .Net 5.0 and not done in .net 3.5): We want to implement the LINQ library. Now, let us size this task ... before the can do so, they need to carefully define all of the stories <strong>IN DETAIL</strong>, and only then try to put it together. Still, the amount of use cases is huge, and interactions between different parts of the system. Without lots of Wiki pages, lots of Word documents, a combination of these two, and perhaps something else, I do not see how they could keep track of things.</p>