title: how does TFS's shelveset model compare to a DVCS?
body: <p>Let's say a person is working in a small team SCRUM environment. Several teams are working on different branches of the same code base. In our team we usually split up into pairs to work on code. Occasionally people need to take time off etc. and it would be advantageous to be able to merge person A's code into person B's codebase. But they often don't want to commit at the end of the day for fear of breaking the build. </p>
  
  <p>This led me to <strong>DVCS</strong> -- well suited to P2P merging and doesn't require "the big commit". A team member suggested that TFS's <strong>shelveset</strong> would be able to do this as well. <strong>How do the two approaches compare?</strong> </p>
  
  <p>Team is currently using Subversion. </p>