What are the 5 key points leading to a good / bad go-live experience?
The go-live experience is an exciting moment in any consultants life… It’s what we do and often it’s why we do it… For our clients it’s often even more thrilling because it’s often their only go live and they enjoy the comradery formed during the often all night(s) affair.
Anyway, these are the areas that I feel contribute towards a smooth go-live experience and by go-live I mean the weekend (usually a weekend) where you execute your plan to move from the old way to the new way of doing things…
1) The plan – Every aspect of the go-live plan needs to be addressed to the smallest detail. This plan should be scaled down to the minute so that the team can be properly scheduled. There should be no surprises.
2) Dry runs – Practice, practice, practice makes perfect. Move the transports, do the communication, do the validation, do the backups (testing the restore), do it all…
3) Communication – Regular, pertinent, to the point communication is key to get the steps to flow seamlessly together
4) Experienced integration partner – Ultimately this is the reason why a client brings on an integration partner. They don’t do this for a living and they need help. Make sure that you get people with good solid experience to put it in otherwise you will have no idea what you are getting.
5) Well organized transport strategy from the get go – QA is used to validate your transport sequence. Follow the same sequence to production and you’ll experience less issues. Too many times I see people fiddling the transport sequence between the different environment and it always leads to issues
I could mention many more but I’d rather open it up to the floor to hear what the other experienced consultants have to say on this matter. What are your thoughts for the top 5 aspects to a good go-live experience?