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.
report on plm implementations
spend hours preparing that report and you throw it away. When starting this phase, if existing documentation or flowcharts are available, this information can be put to good use. However, the currency of this information must be validated. Regardless, and assuming on the availability of the process experts, multiple and iterative white board sessions are a valuable technique to flush out the process flows. For example, in the manufacturing process, the experts would describe: How are raw materials