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.
how to rfp outline
profits, you now decide how to eliminate or, at least, minimize them. The biggest problem encountered in this phase is that project teams and users go hog wild. Let's face it; you are not painting a picture starting with a blank canvas. You already have a charcoal outline in terms of the solution provided by the package software that has been selected. You still need to stay within the lines and, as with colors, ensure that the requirements blend and integrate with each other. In this phase, you expect