Time Schedule of Upgrade

guiguille
Giga Expert

‎06-02-2017 01:27 PM

Hey guys,

I'm preparing a migration from Helsinki to Istanbul. Our current configuration is the following:

  • 3 SN environments
  • 4 developers, 2 testers

Our instance is pretty new, so we don't have a lot of features built. I'm going through the ServiceNow checklist and everything looks good. My only doubt is about timing. My initial time estimation was to do the complete upgrade in 2 weeks and a half, by doing the following:

  1. Day 0, upgrade DEV. QA all my modules and fix the issues in one week.
  2. Day 7, upgrade TEST. Apply update sets from DEV and do UAT. Fix any additional issues.
  3. Day 14, upgrade PROD. Apply update sets and stand by for any missing defect.

My only concern is that if this schema is possible. My idea is to "convert" two devs to testers, and have 4 guys testing the environment and 2 waiting to fix anything that appears.

In your experience, is this timeframe correct? Do upgrades usually take more time? My main concern is being over optimistic, and then having an issue with the client because the upgrade is taking longer than expected (I assume this is the concern we all have when doing stuff like this).

Thanks!

Regards

0 Helpfuls
  • 1,338 Views
2 REPLIES 2

Goran WitchDoc
ServiceNow Employee
ServiceNow Employee

‎06-02-2017 02:22 PM

If it as you say, pretty new instance, not much customized stuff etc. I see no reason why it shouldn't work. Helsinki -> Istanbul is a pretty good upgrade as well since both has service portal etc. My guess is that you won't find so much to fix, it will go on pretty fast. It's mostly your own custom things that breaks 😃



//Göran


guiguille
Giga Expert
In response to Goran WitchDoc

‎06-13-2017 07:12 AM

Hi Goran! Thanks for the answer. I've set the timing as I initially thought. I'll leave the question open for the next month, and come back to leave over here my experience with the upgrade.


0 Helpfuls