Hi DBConsulting,

This is a very good question. My suggestion would be to break the
sub-schemas out as separate forms and use one form that aggregates them
using import. It's difficult to have more than 1 person working on an
InfoPath solution at the same time. Have them work on separate solutions and
combine them later when they have functionality done. Of course, it will be
difficult to copy over the views and retain the binding, but if you preserve
namespace and xpaths of each sub-schema that is aggregated then you should
be able to copy the views into the aggregate solution and the bindings
should preserve. Some stuff like expression boxes won't. In general, the
copy of views isn't 100% fidelity, but it should get you most of the way
there. You'll have to test all of the fields before and after though.

Good luck!