Typically, when you have multiple developers, you assign each one to work on a different project. One developer is responsible for integrating each project in the "controller" project. This one is generally responsible for the logic in your solution and each other project is usually responsible for one adapter and has various functions that can be performed to that adapter. In this way, none of the developer's work conflicts with any other developer's work. Generally, you would use some sort of source control to transfer files between machines and to share changes between developers. SVN is a basic open-source one you might start with.

Thanks tsasnett,

Assume we don't have any SVN for continuous integeration.

there are two developers with their own dev pcs. they are working on same solution with two projects. 

developer 1 works on project 1 while developer 2 works on project 2 seperately. once they endup with development and debugging, developer 2 will send project 2 (pega package) to developer 1 via shared folder or any transfer medium.

NOTE: developer 1 who is also responsible of integration of these two projects to main solution.

is the above assume is correct and can be used as approach?

thanks

Asif

Yes, that would work.