Software adoption

Last updated

In computing, adoption means the transfer (conversion) between an old system and a target system in an organization (or more broadly, by anyone).

Contents

If a company works with an old software system, it may want to use a new system which is more efficient, has more work capacity, etc. So then a new system needs to be adopted, after which it can be used by users.

There are several adoption strategies that can be used to implement a system in an organization. The main strategies are big bang adoption, parallel adoption and phased adoption. "Big bang" is a metaphor for the cosmological theory of the same name, in which the start of the cosmos happened at one moment in time. This is also the case with the big bang adoption approach, in which the new system is supposed to be adopted wholesale on one date. In the case of parallel adoption, the old and the new system are run in parallel initially, so that all the users can get used to the new system, but still can do their work using the old system if they want to or need to do so. Phased adoption means that the adoption happens in several phases, so that after each phase the system is a little closer to being fully adopted by the organization.

Selecting an adoption strategy

The adoption strategy has to be selected before adoption begins, and is chosen based on the goals to be achieved and on the type of system to be implemented. The three types of adoption, Big Bang, parallel adoption and phased adoption, range from an instant switch to a strategy where users progressively start using the new system over a certain period of time (which can be weeks, months or even years).

The actual selection is done by prioritizing the goals to be achieved and then matching a strategy against it (Eason, 1988). Eason defines the following goals:

If a large critical mass is, or might be, needed for the system to work effectively (e.g. due to network effects), a big bang strategy might be the answer. (Rogers, 1995)

Minimising risk to the ongoing operation of the organization can be very important. Parallel and phased introductions might help to control these risks, depending on the situation.

The organization has to be ready for the changeover. Socio-technical preparations such as training sessions and ready-made scenarios must be clear.

If the new system is designed to deal with new requirements, such as business process reengineering, the speed at which the organization is changing over to the new processes or attempting to meet other new requirements.

The system might need to be adjusted to the users needs. In this case, the chosen strategy must provide the opportunity to do so.

Table Eason Matrix

Eason matrix.gif

The actual selection of adoption strategy depends on far more factors then these goals, but they create a window to choose one of the types. Other criteria are called variables (Gallivan, 1996). Gallivan suggests that the appropriate adoption types depends on:

Innovativeness of the individuals
Attributes of the ones that are to adopt the innovation/system

The type of innovation
Is it a process or product innovation?

Attributes of the innovation itself
Preparedness, communicability and divisibility

The implementation complexity.
How complex is the implementation or what is it is extent?

These variables are of a higher level than the criteria of Eason and should be handled as such. Based on table 1 and on the mentioned higher level variables by Gallivan, one can make a selection of an appropriate strategy to choose.

Preparing an organization for adoption

Org prep.gif
Figure 1: Organization preparation Process

In order to prepare the organization for the adoption of the new system, the changes that will take place need to be determined. This is necessary to be able to have a plan or an overview of the changeover, and can be done by creating requirements for the system. Once the management has determined the requirements in a report of determined changes, they need to agree upon them to be able to move on with the change-process. If there is no agreement, the management needs to discuss the requirements again and again until they do agree. If agreement is achieved and the agreement contract is signed, the organization can take further steps. So now the test-phase can be prepared, in which the validity of the data that will be used will be checked and in which trials will be held (Eason, 1988).

In parallel, it is highly recommended that a comprehensive user adoption plan be prepared working together with the business and the affected users. This plan should consider all pre- and post- system rollout communications; user training & documentation; any internal marketing efforts that will be undertaken to drive adoption such as system branding or swag; as well as troubleshooting assistance during the rollout (i.e. extended help desk hours and/or a hotline, and identification of key contacts for each affected business area).

See also

Related Research Articles

Project management is the process of leading the work of a team to achieve all project goals within the given constraints. This information is usually described in project documentation, created at the beginning of the development process. The primary constraints are scope, time, and budget. The secondary challenge is to optimize the allocation of necessary inputs and apply them to meet pre-defined objectives.

<span class="mw-page-title-main">Iterative and incremental development</span> Development methodology

Iterative and incremental development is any combination of both iterative design and incremental build model for development.

In business and engineering, product development or new product development covers the complete process of bringing a new product to market, renewing an existing product and introducing a product in a new market. A central aspect of NPD is product design, along with various business considerations. New product development is described broadly as the transformation of a market opportunity into a product available for sale. The products developed by an organisation provide the means for it to generate income. For many technology-intensive firms their approach is based on exploiting technological innovation in a rapidly changing market.

Rapid application development (RAD), also called rapid application building (RAB), is both a general term for adaptive software development approaches, and the name for James Martin's method of rapid development. In general, RAD approaches to software development put less emphasis on planning and more emphasis on an adaptive process. Prototypes are often used in addition to or sometimes even instead of design specifications.

<span class="mw-page-title-main">Requirements analysis</span> Engineering process

In systems engineering and software engineering, requirements analysis focuses on the tasks that determine the needs or conditions to meet the new or altered product or project, taking account of the possibly conflicting requirements of the various stakeholders, analyzing, documenting, validating, and managing software or system requirements.

Software prototyping is the activity of creating prototypes of software applications, i.e., incomplete versions of the software program being developed. It is an activity that can occur in software development and is comparable to prototyping as known from other fields, such as mechanical engineering or manufacturing.

<span class="mw-page-title-main">Accounting information system</span> System of collecting, storing and processing financial and accounting data

An accounting information system (AIS) is a system of collecting, storing and processing financial and accounting data that are used by decision makers. An accounting information system is generally a computer-based method for tracking accounting activity in conjunction with information technology resources. The resulting financial reports can be used internally by management or externally by other interested parties including investors, creditors and tax authorities. Accounting information systems are designed to support all accounting functions and activities including auditing, financial accounting porting, -managerial/ management accounting and tax. The most widely adopted accounting information systems are auditing and financial reporting modules.

An information technology audit, or information systems audit, is an examination of the management controls within an Information technology (IT) infrastructure and business applications. The evaluation of evidence obtained determines if the information systems are safeguarding assets, maintaining data integrity, and operating effectively to achieve the organization's goals or objectives. These reviews may be performed in conjunction with a financial statement audit, internal audit, or other form of attestation engagement.

Requirements management is the process of documenting, analyzing, tracing, prioritizing and agreeing on requirements and then controlling change and communicating to relevant stakeholders. It is a continuous process throughout a project. A requirement is a capability to which a project outcome should conform.

Business analysis is a professional discipline focused on identifying business needs and determining solutions to business problems. Solutions may include a software-systems development component, process improvements, or organizational changes, and may involve extensive analysis, strategic planning and policy development. A person dedicated to carrying out these tasks within an organization is called a business analyst or BA.

Extreme programming (XP) is an agile software development methodology used to implement software systems. This article details the practices used in this methodology. Extreme programming has 12 practices, grouped into four areas, derived from the best practices of software engineering.

Software project management is the process of planning and leading software projects. It is a sub-discipline of project management in which software projects are planned, implemented, monitored and controlled.

<span class="mw-page-title-main">Phased adoption</span> Implementation strategy

Phased adoption or phased implementation is a strategy of implementing an innovation in an organization in a phased way, so that different parts of the organization are implemented in different subsequent time slots. Phased implementation is a method of System Changeover from an existing system to a new one that takes place in stages. Other concepts that are used are: phased conversion, phased approach, phased strategy, phased introduction and staged conversion. Other methods of system changeover include direct changeover and parallel running.

Parallel adoption is a method for transferring between a previous (IT) system to a target (IT) system in an organization. In order to reduce risk, the old and new system run simultaneously for some period of time after which, if the criteria for the new system are met, the old system is disabled. The process requires careful planning and control and a significant investment in labor hours.

Big bang adoption or direct changeover is when a new system is adopted instantly, with no transition period between the old and new systems.

Performance engineering encompasses the techniques applied during a systems development life cycle to ensure the non-functional requirements for performance will be met. It may be alternatively referred to as systems performance engineering within systems engineering, and software performance engineering or application performance engineering within software engineering.

<span class="mw-page-title-main">Parallel running</span> Strategy for system changeover

Parallel running is a strategy for system changeover where a new system slowly assumes the roles of the older system while both systems operate simultaneously. This conversion takes place as the technology of the old system is outdated so a new system is needed to be installed to replace the old one. After a period of time, when the system is proved to be working correctly, the old system will be removed completely and users will depend solely on the new system. The phrase parallel running can refer to the process of changing a fragment of business information technology operation to a new system or to the technique applied by the human resources departments in which the existing staff stay on board during the transition to a new staff.

In software engineering, a software development process or software development life cycle (SDLC) is a process of planning and managing software development. It typically involves dividing software development work into smaller, parallel, or sequential steps or sub-processes to improve design and/or product management. The methodology may include the pre-definition of specific deliverables and artifacts that are created and completed by a project team to develop or maintain an application.

Small-scale project management is the specific type of project management of small-scale projects. These projects are characterised by factors such as short duration; low person hours; small team; size of the budget and the balance between the time committed to delivering the project itself and the time committed to managing the project. They are otherwise unique, time delineated and require the delivery of a final output in the same way as large-scale projects.

Agile Business Intelligence (BI) refers to the use of Agile software development for BI projects to reduce the time it takes to show value to the organization in comparison to other approaches. It helps in quickly adapting to changing business needs. Agile BI enables the BI team, business people or in general stakeholders to make better business decisions, and to start doing this more quickly.

References

.