Many times on larger BizTalk projects developers need to share working inside Projects and Orchestrations. This means at some point you will have conflicts. While Visual Studios offers the option to Auto-Merge files, I have not seen this done successfully with BizTalk Orchestrations.
Here are 5 simple rules for simplifying and streamlining large scale BizTalk Orchestration Development.
I recently published another article with other good practices to follow when developing orchestrations: matricis.com/.../orchestration-maintainability-practices-microsoft-biztalk-server
I'm ready to branch out a bit such as enterprise level development or using some of MS's other servers like BizTalk Development