Experiencing Salesforce application transition
I have just come out of Salesforce application transition work. Unlike few other transitions, the recent one made me realize that indeed a major cost saving can be done by adopting 90:10 offshore-onsite model while maintaining full efficacy. Let me refrain here from writing basic transition model guideline but I would probably like to share my experience and few techniques which I found very handy and practical in its usage which increased the effectiveness level in this offshore based transition model.
Most of the times, customer intends to transition their application with an intention of cost saving and improving their business processes, IT turnaround time on resolving application related issues and management focus on having robust knowledge management system in place. With SFDC being a niche skill, at times, customers spend a lot hiring expensive subcontractors through third party agents where the tendency might be to deliver irrespective of focusing much on client specific process and without really caring customer's knowledge management needs.
Before moving to transition it may be good idea to do a due diligence exercise and prepare your transition plan (what you think of this new transition). Do not expect much from the customer here as they might be equally unknown to the application maintenance and support need and hence they are looking for your help. But, they can help you understand the functional aspect of applications and few documents on an adhoc basis. Any information or type of documents should be strictly analyzed to get the maximum input. Information might not be available in a sequential order but you can definitely extract the maximum out of these fragmented pieces of information. During transition, it is observed client places at least few of their IT analysts to help and co-ordinate during the transition. Ensure you have right mix of functional and technical resources for this transition. While the functional folks will help in understanding the application and assimilate end to end view at faster pace, the technical folk will do more hands-on on the technical aspect of application. Do not forget to identify right SME for the transition as buying their time in advance is a critical success factor of any transition.
Ensure you initiate KT sessions in the most convenient common time you have between offshore and onsite locations and the session is fully recorded for whatever duration it happens. Your onsite counterparts will be able to play bigger role here. While half day session can focus on knowledge handover, the second half can focus on understanding their code artifacts with respect to SFDC configuration, customization, integrations and necessary downstream systems. You will need your technical folks here. Whatever activity you do, ensure MoM is circulated on daily basis and SMEs review them and provide you regular review comments.
On daily basis, you can also document the theory session you have and make it a living document. Remember, this is something which your customer might be looking for long time and he gets that from you as one of the key deliverables of this transition. This will seed the confidence in client. Discipline is very important all the way and it should remind you of the school days when you were guided by your school teacher. Establishing that sort of rhythm with SMEs is also important.Be focused and proactive in terms of demanding what you really need for understanding their system. Since, the session details are anyway known in advance (you get it confirmed before starting the transition), prepare exhaustive questions for SMEs well in advance so that you utilize the session time appropriately.
As soon as first phase of transition is over and we become conversant with the new system, the tendency may develop to solve their long pending defects/enhancement on a fast track basis to please the customer but this should be avoided. Focus at this stage can be more on developing your own quality and understanding the bigger aspect of application rather than increasing the ticket closure count.
While it is good to have all team members in transition from start of the first phase, it may not help in having everyone in the same sort of discussions when you are moving into next phase of work i.e. Shadow/Primary support. By this time, you should have understood the team and ready to map them with corresponding counterparts who have been providing you this transition. After all, idea is identify the new SME for the application support from tomorrow. To-Be SME should start liaising and discussing with As-Is SME of the application. There can be situation where your SME may take your question in a light way due to variety of reasons primarily since they are much experienced in same field for last many years. This should not dither you in asking what you really feel is right for supporting application from tomorrow.
No big transition runs generally without risks and it's just an ideal scenario to imagine that you have understood everything in just couple of months of transition work where SMEs have been working for last several year. Hence, whatever area you are not comfortable with, highlight them and ensure you spend more focus on them once you have moved to steady state.
I invite your suggestions here in order to bring more effectiveness with fully offshore based transition.