Committing changes in SCC is one of the tasks where you're guaranteed to have to cooperate with other team members. There are practices that can help make committing your changes much smoother. As the saying goes, "we can do this the hard way, or we can do this the easy way." The root cause of most commit pain is merge conflicts. The person at fault is always the person trying to commit and you'll usually not get much sympathy from the rest of the team, especially if they ascribe to the practices discussed in the following sections.
When you commit your changes to the repository you run the risk of having a merge conflict. This conflict can be recognized by the SCC system (such as when two people modified the same file) and simply be rejected, or it may be more severe. You are certainly capable of committing a change that doesn't cause the SCC system to recognize a conflict, yet there could still be a conflict at the code or...