IT projects

Management often bemoans that IT projects fail to deliver on time and within budget. And the truth is that the IT spending waste in our industry it is sometimes suggested confusing. F. Curtis Barry & Company, we currently have four clients, ranging in size from $ 7 million to 650 million dollars in sales of all face similar problems, and budget, as an attempt to create a new order and inventory management systems . Another client invested $ 350,000 with one of the leading OMS companies, but after an unsuccessful implementation of the project.

Why this waste? It is a lack of project management at customer and vendor. Here are some tips, based on the experience has taught us to help you avoid the same fate with your IT implementations.

* Beginner to treat. Some projects would simply never. Usually begins when management accepts the vendor selling the proposal, indicating error. Take the case of one of our largest clients: They fought two years working with the vendor, basically to rewrite most of the system. The client is determined because there is a huge potential ROI. But while big deal for the seller happens when, while their commercial systems path. Customer must have looked at the proposal more realistically at the beginning.

* You must have a plan. Seller of the full text of simple graphs and bar charts. The actual plans for complex systems requires the implementation of all information to be considered, agreed and planned. One mistake, that they are not scheduled weekly updates that you can use to get started, but often it is updated. Plans often do not have dependencies into account all stakeholders continually surprised, because the major Subtask is not synchronized with each other.

* Who is responsible? Both customer and vendor, a project manager. Too often the customer leaves the suppliers and it is a bad idea. For one thing, the seller knows that your business or organization. Second, it is expensive. You will manage the process and implementation.

* How often we speak? As you know, systems projects involve a series of oral and written communication with the evidence constantly passing back and forth. It seems on the surface that you have talked several times a day. But it is really no problem. You have weekly meetings between the two parties to be implemented in two project managers, review of the entire project and timetable for setting targets and, if necessary. Other critical parties can and should participate, if available. Two project managers should circulate the updated agenda and minutes. When you are within 30-45 days, you must map conversion meeting daily. This is an excellent way for all parties to stay together and get done is done.

If you commit to follow these basic religious, everything else should fall in line. As a result, you get a much better chance to implement IT projects on time and within budget.

Article by F. Curtis Barry, helps you manage your warehouse management systems, control systems and a view of your inventory management systems.