Using Shelvesets to Set Aside Pending Changes (Team Explorer Everywhere)

By creating a shelveset, you can set aside a batch of pending changes from a workspace temporarily. You can later restore those changes into your workspace or into the workspace of another user, or you can delete the changes.


Scenarios in Which to Consider Shelving.

You shelve your pending changes when you are not ready to or cannot check in a set of pending changes, as in the following scenarios:

• Interruption - You can shelve your pending changes to set them aside if you are not ready to check them in but you must work on a different task.
• Integration - You can shelve your pending changes and ask your team member to unshelve them if you are not ready to check in but you must share changes with another team member.
• Review – You can shelve changes that must undergo a code review before you check them in. After you create the shelveset, you inform the code reviewer, who can then unshelve and review your changes.
• Backup – You can shelve changes that you want to back up before you are ready to check them in. By creating a shelveset, you copy the changes to the version-control server.
• Handoff – You can shelve changes that are in progress before you hand them off to another member of the team for completion.

taked from : Microsoft (MSDN)