How do you go about defining the requirements of large package systems, particularly those with the all-encompassing scope of ERP, EAM, and CRM software, and still satisfy the needs to the project team, the user community, and executive management? It’s a balancing act rivaling the circus performer trying to keep all of the plates spinning at once. While it is difficult to say one aspect of a project plan is more important than another, accurately and completely defining the needs to be fulfilled by the software is critical to the overall success of the implementation and the longevity of software. This article outlines a logical process for defining the requirements and keeping the plates spinning.
investment proposal documentation
the most of your investment in the software. The enhancement alternative can have long-term impact in terms of costs and support. As Olin Thompson stated in his article on software modifications, Should You Modify an Application Product , Are modifications bad? The answer is yes. A good rule of thumb is that an enhancement today will cost an additional 20% each time the enhancement has to be retrofitted to a new release. Assuming that the initial cost of enhancement was $50,000 and at least one new