Many enterprise customers have implemented multiple Salesforce orgs. There is often a need to consolidate these orgs into a single org due to standardization of business processes and the demand from users to work in an integrated environment. Consolidation is also required when businesses discover more interdependencies between the processes
We will talk about how an existing Salesforce org can be assessed. Here are the needs for Org assessment: When a system integrator is taking over an org from an existing support team to perform production support and continuous application development In case of an implementation of a fresh org
Maintaining the integrity of a project team’s roles and responsibilities is most important for a CRM implementation. If not paid attention to, this becomes a major risk on implementations and that is why I am writing about this here. Integrity is often compromised due to mismanagement of resources and as
Enterprise stakeholders often complaint about user adoption for CRM applications. There are many scenarios where a CRM application is built but the usage/adoption is nil. This can be due to many reasons: Application is built in a silo. End user feedback is not incorporated Poor data quality– At the time
We are often asked to scope out and estimate the work effort on greenfield and ongoing CRM implementations. Here is the methodology that can be used to scope, estimate and resource load an implementation. I have prepared the methodology for Salesforce implementations Prepare Estimation Factors Put hours against each estimation
Comments