About Us
March 24, 2010 from Toolbox for IT – “In many cases the ERP project plan is not worth the paper on which it is printed. Worse yet, many project managers shoot themselves in the foot by pre-maturely committing to a project plan that sets the wrong management expectations. The problem is once cast, expectations will not go away and only come back to haunt you later. Could this be one reason why many ERP projects “fail”?
Even when the schedule and budget are “formally” published, inadequate definition of project scope (and boundaries) is a major reason the plans are invalid and quickly tossed out the window. In other words, we need a project scope, schedule and budget that closes expectation gaps. A project plan people can believe and use to actually manage the project. What a crazy idea!…”
180 View – The author provides 13 dimensions to consider. Unfortunately, a requirements document is not one of them. Requirements need to be tightly defined in advance of the selection of an enterprise system, and the implementer should define scope as their response to the requirements. In fact, make the vendor response to the requirements part of the contract.
Go Back
