Tquila works with some of the largest enterprise companies in the world. Often we’re brought in to discuss architectural strategy whether this is before the first Salesforce project kicks off or some way down the line when they’re looking for some feedback on their current state.
A common question that comes up from our larger customers is the question as to whether they should have one or several Orgs, and I was in the process of creating a whitepaper when I noticed that salesforce.com has done this already!
I would however add one more line to their “Single Org versus Multiple SF Orgs Capability Matrix” which would be:
|Capability||Single Org||Multiple SF Org||Other Considerations|
|Development process & team organisation||Complex if there are several delivery teams especially if release cycles differ. Simple if there is a single team on a single release schedule||Simpler but may result in redundant code and libraries||Both approaches need an enterprise architect but in slightly different coordination roles|
Perhaps you have some lessons that you’d like added to the whitepaper too?