Product software implementation method

ABold textOrganizational and quality management will embrace this view, as a strict usage of any method results in more clarity on organizational level. Change == management however might indicate that more flexibility in an implementation method leaves more room for the soft side of implementation processes.

Implementation frameworks

Apart from implementation methods serving as the set of rules to implement a specific product or service, implementation frameworks serve as the project managed structure to define the implementation phase in time, budget and quality.

Several project management methods can serve as a basis to perform the implementation method. 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. The applicability of using a framework for implementation methods is clarified by the examples of using DSDM and Prince2 as project management method frameworks.rony

=DSDM===

The power of DSDM is that the method uses the principles of iteration and incremental value, meaning that projects are carried out in repeating phases where each phase adds value to the project. In this way implementation phases can be carried out incrementally, adding value to for example the degree of acceptance, awareness and skills within every increment [F. Von Meyenfeldt, Basiskennis projectmanagement, Academic Service 1999]. Besides in the management of chance scope, increments are also usable in the process modeling scope of implementation phases. Using increments can align process models of business architectures and product software as adding more detail in every increment of the phase draws both models closer. The DSDM also has room for phased training, documentation and reviewing.

The image below illustrates how implementation phases are supported by the usage of DSDM, focusing on management of change, process modeling and support.

Prince2

As DSDM does, the Prince2 method acknowledges implementation as a phase within the method. Prince2 consists of a set of processes, of which 3 processes are especially meant for implementation. The processes of controlling a stage, managing product delivery and managing stage boundaries enable an implementation process to be detailed in with factors as time and quality. The Prince2 method can be carried out iteratively but is also suitable for a straight execution of the processes.

The profits for any implementation process being framed in a project management framework are:

Clarity

An implementation framework offers the process to be detailed in with factors such as time, quality, budget and feasibility.

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).

Embedded & Generic methods

One way to implement product software is through usage of an embedded method or model. Embedded models are part of the auxiliary materials (see: definition of product software) that come with the software package.

Implementing a software product using an embedded model implies not only that the model is (mostly) only usable with the specific software product, but also that the product can or should only be implemented using the model. Embedded methods can thus be seen as very specific ways implementing product software.

Examples of software products with an embedded method are:

Implementing SAP (SAP R/3), using the ARIS embedded model.

Implementing the Baan ERP system, using Dynamic Enterprise Modeling (DEM).

Implementing Oracle E-Business Suite, using Oracle Application Implementation Method (AIM).

Generic implementation methods are not meant for a specific software product but for common usage in implementing product software products. This usage is going to be elaborated on using the example of implementing product software using Object Process Methodology. This methodology is very useful in for example ERP modeling: the modeling of ERP systems in order to implement it into an organizational structure.

Assessments

Using an embedded method brings the power that the method is designed to implement the software product that the method comes with. This suggests a less complicated usage of the method and more support possibilities. The negative aspect of an embedded method obviously is that it can only be used for specific product software. Engineers and consultants, operating with several software products, could have more use of a general method, to have just one way of working.

Using a generic method like ERP modeling has the power that the method can be used for several ERP systems. Unlike embedded methods, the usage of generic methods enables engineers and consultants that operate in a company where several ERP systems are implemented in customer organizations, to adapt to one specific working method, instead of having to acquire skills for several embedded models. 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.