One of the most common mistakes that a novice analyst can make is the failure to fully consider the risks associated with the different conversion strategies. The analyst will most like just assume the the best way to go isdirect conversion.
Another most common mistake is leaving the document till the end and not having enough time to produce a sufficient document. I think of procrastination, and I'm sure everyone can relate to procrastination at some point in their academic career (whether it was a project, studying, or homework).
Another common mistake is not considering the increase of cost. When converting simultaneously the firm has to hire more programmers to run the systems. The cost can increase for the people who work with the system based off of their salaries.
I think that another mistake that is often made is that analysts may push a new system too quickly. Often, organizations want to implement something quickly, and important aspects become overlooked. This can cause some serious damage if the new system negatively impacts an organization.
I think rushing the process is one of the most common and major errors made by novice analysts. I think it happens both out of procrastionation and at times overzealousness. When things get rushed little mistakes are often made and overlooked, which have to be readressed later adding to overall cost.
To go off of Sade’s comment I would also like to add that another down side to push a system to quickly is that you might have more resistant adopters than the normal 20%-30% and less ready adopters because people want to be given the chance to adjust to the new system before they are just thrown into using it and like Sade said cause there to be negative impacts on the organization.
As a side note, a migration plan should be made to ensure the business can continue its operations even in the event of technical glitches in the new system also called the business contingency plan. The plan has to ensure that the people who will be affected by the new system are ready and able to use it.
I would say that a mistake might be not running a pilot test first. Organizations often select one or more location to convert first as a pilot test and if successful implement throughout the organization. I believe that if this is not done then the new system may have too drastic an effect on employees.
Cost can be a major issues, especially in parallel conversions. When an organization is running two systems at the same time it will take twice as long to check each system, and cross check between the two systems to make sure they are operating properly. Updates will also need to be made to the old system to make sure it can work with the new one.
One of the three common mistakes that novice analysts make in migrating from the as-is to the to-be system I would say is time. When novice analysts migrate from the as-is to the to-be systems they forget to consider time. This can involve the novice analysts forgetting to consider how long the process to migrate from the as-is to the to-be system can take, which also includes all the tasks to complete.
One of the most common mistakes that a novice analyst can make is the failure to fully consider the risks associated with the different conversion strategies. The analyst will most like just assume the the best way to go isdirect conversion.
ReplyDeleteAnother most common mistake is leaving the document till the end and not having enough time to produce a sufficient document. I think of procrastination, and I'm sure everyone can relate to procrastination at some point in their academic career (whether it was a project, studying, or homework).
ReplyDeleteAnother common mistake is not considering the increase of cost. When converting simultaneously the firm has to hire more programmers to run the systems. The cost can increase for the people who work with the system based off of their salaries.
ReplyDeleteI think that another mistake that is often made is that analysts may push a new system too quickly. Often, organizations want to implement something quickly, and important aspects become overlooked. This can cause some serious damage if the new system negatively impacts an organization.
ReplyDeleteI think rushing the process is one of the most common and major errors made by novice analysts. I think it happens both out of procrastionation and at times overzealousness. When things get rushed little mistakes are often made and overlooked, which have to be readressed later adding to overall cost.
ReplyDeleteTo go off of Sade’s comment I would also like to add that another down side to push a system to quickly is that you might have more resistant adopters than the normal 20%-30% and less ready adopters because people want to be given the chance to adjust to the new system before they are just thrown into using it and like Sade said cause there to be negative impacts on the organization.
ReplyDeleteAs a side note, a migration plan should be made to ensure the business can continue its operations even in the event of technical glitches in the new system also called the business contingency plan. The plan has to ensure that the people who will be affected by the new system are ready and able to use it.
ReplyDeleteI would say that a mistake might be not running a pilot test first. Organizations often select one or more location to convert first as a pilot test and if successful implement throughout the organization. I believe that if this is not done then the new system may have too drastic an effect on employees.
ReplyDeleteCost can be a major issues, especially in parallel conversions. When an organization is running two systems at the same time it will take twice as long to check each system, and cross check between the two systems to make sure they are operating properly. Updates will also need to be made to the old system to make sure it can work with the new one.
ReplyDeleteOne of the three common mistakes that novice analysts make in migrating from the as-is to the to-be system I would say is time. When novice analysts migrate from the as-is to the to-be systems they forget to consider time. This can involve the novice analysts forgetting to consider how long the process to migrate from the as-is to the to-be system can take, which also includes all the tasks to complete.
ReplyDelete