An oldie but goodie… part of my original series of Enterprise Architecture on Salesforce.com and published on August 22, 2014
I’m a huge fan of the SFDC platform. It has the potential to transform businesses if implemented and managed correctly. Unfortunately I’ve seen many companies come up short when trying to reap value from Salesforce. There are countless reasons for this but here are some of the top reasons I’ve seen:
- No organizational vision or direction for the company’s use of Salesforce
- No roadmap and product management strategy that ties the platform’s use to corporate goals.
- No formal architecture, governance or change management strategy leading to an evolutionary design of either silo’d functionality or a mis-use of multiple Salesforce instances.
- The original implementation was delivered with little-to-no technical understanding by the customer.
- A lack of understanding between how and when to use configuration vs custom code.
- The implementation consultants delivered “functional value” only and therefore lack any standards in the configuration design and coding layers.
- There are no patterns, no modularization, and no chance to extend the functionality without significant refactoring.
- Test coverage is completed only as an after thought and lacks any kind of design or assertions. There is a high risk you will break something when you change configuration or code.
- Lack of any forms of living documentation that capture your design and the reasons for that design.
- Unwillingness or inability to retire legacy systems has kept people from using the system.
- Lack of training or communication to end users
- Data Quality in the new system is low and the outputs of the system are not trusted
So how do you prevent these types of issues? How do you fix them if you are already a victim of this problem? My recommendation to you is this: Build an Enterprise Architecture with Salesforce.com
How do you do this? It is not easy and it will take time, money, and platform knowledge. But if done correctly Salesforce can become a differentiator for your business.
This post and the ones that will follow it will walk you through the process of establishing an EA for Salesforce. The main framework I am using is the TOGAF Architecture Development Methodology. If you are not familiar with TOGAF, I recommend reading up a little on the framework. TOGAF is an approach for designing, planning, implementing, and governing an enterprise information technology environment and is an open standard of The Open Group Architecture.
The TOGAF v9.1 Architecture Development Methodology from The Open Group
Throughout the post I will follow the phasing of TOGAF and point out some relevant questions and considerations as you shape your Salesforce Architecture. That being said here is roughly the process you will follow as you build your plan:
Define Your Architectural Vision for Salesforce
- Who are your stakeholders and your business goals?
- What are the corporate goals that will influence your vision?
- What are your architectural principals?
- Where is your architectural repository and how will you manage your artifacts?
Design Your Business Architecture and Strategy
- What Lines of Business will use Salesforce?
- What are your business requirements?
- What business processes will be implemented on or influenced by SFDC?
- What building blocks of your business will be built on SFDC?
- What is your org strategy?
- Who are your actors and possible license choices?
Design Your Information System Architecture
- How do you design an Application Architecture on SFDC?
- How do you design a Data Architecture for SFDC?
- What is your application rationalization plan? What will be added or retired with SFDC (and when)?
- What is your Gap/Fit and what will you do about it?
Design Your Technology Architecture
- What is your integration architecture?
- What is the right architecture for custom development?
- How will you manage your technical environments?
- What are your technical risks and how will you mitigate them?
Design Your Implementation plan
- What is the right methodology to use?
- What is your SFDC Architectural maturity?
- What is the appropriate release strategy?
- How do you build a roadmap?
Plan your migrations
- What is your Cost/Benefit analysis for each release?
- What are you project dependencies?
- What is the right deployment strategy?
- What is your test strategy?
- What is your data conversion plan?
Design your governance plan
- What groups will you need to integrate your efforts?
- How do you establish an effective CoE?
- What is an Architecture Review Board?
- How do you setup a system administration model?
- How do you manage your vendors?
- How will you ensure adherence to your architectural design and standards?
Define your Change Management Plan
- How do you effectively manage change?
- What types of changes can be made in production and by who?
- What types of changes should be made in a project vs bug fix?
My recommendation would be to walk through the list in order and try to answer all of the questions at least once — to the best of your ability at the time. Then return to back to the first section (architectural vision) and start to refine into a deeper level of detail. TOGAF is cyclical and so too is your design and implementation of an EA for SFDC. It follows the concept of continual improvement that will evolve each time you iterate through the cycle. So get busy and build out your EA for SFDC. Your users, your technology teams, and your business stakeholders will thank you for it.