title: Recommended TFS branch structure for multiple developers
body: <p>I am no TFS Master. In my previous company I've used tfs for source control but it was already structured by some consultant. The structure is like this</p>
  
  <pre><code> $/Main
      -Project Framework
      -Project Application
      -Project Utilities
      -Project Web
    -Development
      -Project Framework
      -Project Application
      -Project Utilities
      -Project Web
    -DEV1
       -Project Framework
       -Project Application
       -Project Utilities
       -Project Web
    -DEV2
       -Project Framework
       -Project Application
       -Project Utilities
       -Project Web
  </code></pre>
  
  <p>After each development we would check in to our node, then merge to development, check in then merge to Main and check in.</p>
  
  <p>Now I'm a new company and we did the structuring on our own. Our current structure is just</p>
  
  <pre><code>$/Main
    -Project Framework
    -Project Application
    -Project Utilities
    -Project Web
  </code></pre>
  
  <p>I suggested that we do the same thing like my previous company but I can't explain why. In my mind the reason why I wanted it is so that if I accidentally mess the project I can still pull the development copy, and main copy is always the approved or working code.</p>
  
  <p>am I right?</p>