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.
definition of white paper
deliverables from the requirements definition task. This task consists of the As Is, To Be, and Gap Analysis phases. As depicted below, a progression through these phases should provide users with a clear vision on the operation of the software. As we will see later, the typical sequence of these phases is As Is, To Be, and, then, the Gap Analysis. The software that you purchased acts a bridge to get you all or part of the way to the To Be environment. The Gap Analysis will determine how much weight this