What is meant by "bite off more than you can chew" in an ERP implementation?

i agree Mr Tohamy 

I Agree with Rehan Qureshi. In addition to that the most important question is How flexible is this system? If, for example you were about to purchase a payroll system that does not allow for third-party integration, unless it’s with the vendor’s preferred partner, find a different vendor. No company should be tied to propriety software that does not allow for data integration. That’s a1980s type of mentality by a tiny number of software vendors, who are slowly shrinking into oblivion. The best software companies, today allow for integration into their applications, whether its; CRM, ERP, HRIS, Time and Attendance or Payroll Software.

ERP is a task which needs to done in very systematically and predefined phases as per the cricticality of work, which should be analyzed on priority basis.

What I feel practically, is that, we should not start to perform all the modules of ERP all-together for their implementation in the working system, otherwise we cannot customize the ERP as per needs and also we cannot implement on time which leads to heavy losses.

ERP implementation is herculean task, with single implementation you are trying to change everything in the organization, Its culture, people, methodology how everyting will happen and the entire process and way of doing your routine job. It not only demands change around you but also to relook what you are suppose to do with responsibilty and accountability and to overcome this task implementation is done in phases so that sudden change should not shut everything and bring strong resistance by users.

Agree with Mr. Rehan Qureshi

BITE OFF MORE THAN YOU CAN CHEW

There are two ways to try to do too much too fast with an ERP implementation. One is to try to implement too much with regard to geography or sites all at one time. Some ERP vendors and implementation providers advocate the “big bang,” encouraging companies with multiple locations to take their entire organization live all at once. But often, that proves to be too much for an organization to handle. In many cases, it is better to implement an enterprise application at one or two sites at a time. This allows a company and its implementation consultants to work kinks out of the business models and process flows that were decided upon by the implementation team. Another way to bite off more than you can chew is to make too many dramatic changes in your organizational culture all in one felt swoop. When you buy packaged software, you are not only buying technology, but a way of doing business that can improve the efficiency of your organization. In many cases, elements of an application’s functionality may represent business practices that you currently do not engage in, either because they have not been a part of your corporate culture or because they are not supported by your legacy system. Each of these process improvements and best practices are likely good opportunities to move your business forward, but trying to implement all of this functionality at the same time may prove to be too much for a business’ management structure and employee base to absorb. Consider that Vitamin C is a very good thing, but trying to take too much of it at one time can upset your stomach! In order to avoid disruption that can result from change that comes too quickly, it often makes sense to take a more gradual approach. At the initial implementation, reach out to your functional leaders to see whether or not adding various elements of new functionality creates too great a burden. Sometimes better to go live with functionality you currently have in your legacy system, and then schedule add-ons when you are genuinely ready for them after an initial stabilization period. 

I AGREE WITH MR  MOHAMMED IQBAL ABUBAKER

MEANS TAKE A LONG BREATH, HOLD YOURSELF , DO NOT  GET INVOLVE IN TOO MANY MATTERS. ONE JOB AT ONE TIME.

There are many ways to try to do too much too fast with an ERP implementation.

·         Implement all ERP modules irrespective of your critical requirements.

·         Overload your implementation team capacities.

·         Adopt the "big bang" approach and roll implementation in more than two sites at a time.

·         Attempt to implement all modules' functions irrespective of your critical requirements.

·         Employ poor or no change management plan.

But I do not understand

this concept leads to failure

sorry I do not know