This entry focuses on the process modeling (Process Modeling) side of the implementation of “large” (explained in complexity differences) product software, using the implementation of Enterprise Resource Planning systems as the main example to elaborate on.
An example of “larger” product software is the implementation of an Enterprise Resource Planning system.
Next, the usage of an ERP system involves much more dedication of the end users as new tasks and responsibilities will either be created or shifted.
In this case, two alternatives are possible: the customization of the software or the redesign of the organizational structure, thus the business processes.
Customizing however results in a situation where the organizational integrity is not adjusted, which puts less pressure on the end users, as less changes or shifts in workflows are required.
This choice leaves more room for situational factors that are not taken into account in the chosen method, but will result in ambiguity when questions arise in the execution of the implementation process.
Since this entry focuses on the implementation of product software, the best project management methods suitable for supporting the implementation phase are project management methods that focus on software and information systems itself as well.
In this way implementation phases can be carried out incrementally and add value to important project aspects such as the degree of acceptance, awareness and skills within every increment [F. Von Meyenfeldt, Basiskennis project management, Academic Service 1999].
Iterative, incremental approach As explained, the possibility to execute different phases of the implementation process iteratively enables the process to be executed by incrementally aligning the product to be implemented with the end-user (organization).
This usage is going to be elaborated on using the example of implementing product software using Object Process Methodology.
Engineers and consultants, operating with several software products, could have more use of a general method, to have just one way of working.
Generic methods have however the lack that implementation projects could become too situational, resulting in difficulties and complexity in the execution of the modeling process, as less support will be available.