If you would like to make a request for any development changes, please contact your Account Manager or the Account Management Team on +44 (0) 208 328 9814 or email@example.com.
They will discuss the required changes with you to get as much information as possible in order to estimate the effort required.
You will then be provided with an Order of Magnitude (which we call an ‘OOM’!) This is a high level ball-park estimate. If it is in line with your expectations we can then go on to writing up the quote with detailed specifications included.
Once the quote is approved resources will be allocated for the work to be done. Changes will always be carried out in either development, UAT or a testing environment. When the work has been completed you will receive a ‘release note’ and now it’s your time to test (see below!)
Once you have approved then we will agree with you a convenient time to make the change live.
Testing – how on earth do you do it?
Whenever you request changes to your system, update or implement new processes, undertake a project or do pretty much anything that would mean something changes in your system you will need to TEST!
But what does this actually look like and how do you do it? Here’s our 3 step guide to testing like a pro:
1) Always do your testing in the test environment (you’ll hear us use the phrase ‘User Acceptance Testing’ or ‘UAT’). It is in the development, UAT or testing environments that you should do your testing.
2) Start with the easy bits. Test the specific changes that you requested. If your change was a development change then you will have a release note with the testing recommendations for you to follow. If your change was a process change you won’t have a release note but you should work through the exact process that you discussed with your consultant.
3) Use your imagination! Now comes the time to see how the change could affect all other users and departments. Here you have to think as broadly as you can! Imagine all possible scenarios where your change could have a knock-on effect. For example: You’ve changed the way you key-in sales orders which works perfectly for you but now the figures on the ledger is not what your accounts team would expect it to be.