Managing Blueprint Publishing with Multiple Developers

Our company has been using Cherwell for a couple years, but generally speaking the majority of the development has gone through a single developer.  As the usage of Cherwell grows, so does the level of development work.  We are in a position now where we will need to add more full time Cherwell developers.

When we've done work in the past with having multiple developers, there has always been the risk of stepping on each others work by overriding changes due to publishing a separate blueprints that overlapped in various objects.  We realize communication is a key piece to making sure things are done in proper order and we limit the scope of what's included in the blueprint.

Does anyone have some advice or best practices for how to handle Cherwell blueprints when you have a team of developers making changes?