We are moving to a new ERP some time in the fall 2018.
There are some considerations to work concurrently. I have always been of mind to get on the new horse and not look back.
What are your preferences in this scenario? Both solutions are hosted. I think concurrent is a lot of extra work. And you can't bill twice. What are the advantages of concurrent? Saving Changes...
The big driver for a 30-day concurrency period is less about user testing and more about the data being consistent and correct. If the new ERP output fails in the correctness of data output, staff can quickly switch back to the still running old system to resume operations.
For example, say the ERP is responsible for payroll - your data output from both systems should be identical. Once staff have confirmed this output is correct and consistent over a 30-day or 60-day period - you can disengage from the old system and move entirely to the new.
This way staff managing payroll are confident in the new system (buy-in is always good!) and you will not be gambling with staff paychecks. Payroll clerks will grumble at having to perform double data entry, but it is a considerably smaller price to pay than having to scramble and correct a failed month of payroll for an entire company.
On the other hand - if the ERP is only managing payroll for less than thirty (30) employees, the running of two ERP systems may be cost prohibitive. Or, just flipping the switch to the new system and allowing payroll to make corrections (if any) will be seen as a quicker less cautious approach.
Best to consider the company/stakeholder risk appetite on the matter before making a final decision. Saving Changes...
To add to Conrad's great feedback, if you will be impacting a large group of stakeholders then concurrent enables you to phase in the change by user group. Of course, given this is an ERP system, isolating groups to enable successful concurrency might be challenging but it may simplify your change implementation effort as those early adopters could become strong advocates with their peers for the change.
Kiron Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Trying to put this on terms of a role you can find inside the PMI I will say that business analyst is accountable to help the organization to decide on that. When you search for related documenation you will find there is an specific task named "needs analysis". Just to comment I am doing this in theory and practice here an article I wrote and was published in PMI and IIBA official newsletters as "best practice" with the aim it can help you:https://www.projectmanagement.com/blog-pos...-right-solution My last comment is: no matter you take this way or any other way to help the organization to understand the impact I firmly believe that you are lost. I was part of one of the hughest initiatives in the history of the organziation where I am working today and it was relating to use or not to use a new ERP or to keep the ERP installed at this time. Saving Changes...
"There is a theory which states that if ever anybody discovers exactly what the Universe is for and why it is here, it will instantly disappear and be replaced by something even more bizarre and inexplicable.
There is another theory which states that this has already happened."
