Migrate To New Technology
Migrate To New Technology
INFORMATION SHEET
This module defines the competence required to apply skills and knowledge in using new or
upgraded technology, with the knowledge, skills and right attitudes.
Compatibility
New technology will need to work with existing hardware, system and application software with minimum changes to
both.
Interoperability
The new technology must be able to interoperate with the existing network.
Maintainability
The current IT staff should be able to maintain the system even after the introduction of the new technology.
Centralisation/accessibility
The new technology must be accessible by multiple users at various sites.
Security
The new technology must be accessed by authorised users only.
Ease of use
Existing users must be able to operate new technology with minimum re-training.
Scalability
The system introduced using the new technology should be able to cope with growth of the business, expansion of
networks, and a growing number of employees, etc.
Evaluating and selecting new technology
Usually there is a gap between what new technology promises and what it actually delivers. This gap will be narrowed
if you align the new technology with current business needs and IT strategy of the organisation. Reducing this gap will
result in maximising benefits of the new technology.
How do you evaluate whether the new technology is successfully aligned with the business requirements?
There are several tangibles (e.g., cost savings) and intangible (e.g., user satisfaction) benefits of implementing new
technologies. These benefits will give you an indication of how well the new technology is aligned with the business
objectives. Therefore, before new technologies are introduced, an organisation’s management must agree on the
performance indicators that will help them calculate and measure benefits after implementation.
• tasks involved
• resources required
• schedule
• milestones
• Organisational issues.
Timing
Timing is an important consideration if the implementation is to go smoothly. The adoption of new technology can place
an additional burden on staff having to deal with disruption to their normal workflow. Most departments have peak
periods of activity that should be avoided. For example, an accounting department’s busiest time is the end of the
financial year; therefore, this period is definitely not suitable for any implementation of new technology.
Tasks
What are the things that have to get done to implement the new technology? The implementation plan should clearly
identify these tasks and schedule them in an appropriate sequence. Installing a network, for example, will have a different
set of tasks from installing a new software system.
Table 1 shows the tasks required to install new PCs for a group of users.
Table 1: Tasks for installing new PCs
Task Description
1 Back up files on existing computers
2 Remove existing computers
3 Install new computers
4 Test new computers
5 Restore files to new computers
Identifying the tasks and their sequence beforehand should ensure that the implementation goes smoothly. This is a very
simple example, but can you imagine what would happen if Task 2 was performed without performing Task 1?
Resources
Having identified the tasks, the next step is to allocate people and resources to them. To minimize confusion, people
need to know exactly what they are supposed to do. Obtaining resources may involve negotiating with the people
involved or their superiors as they may have other commitments. Table 2 provides an example of resources required for
installing new PCs.
Table 2: Resources required while performing implementation tasks
Schedule
After assigning resources to each task, the next step is to determine how long each task will take to complete. Work out
the start and finish date of each task. Then communicate this to those involved so that they know exactly when particular
tasks are to be done. Table 3 below shows the start and finish dates for each task so that staff know when the tasks are
to be completed. This means that your plan should provide a picture of:
• what is to be done
• who is to do it
• when it is to be completed.
Table 3: Task duration
Task Description Resource Start Date Finish Date
1 Back up files on existing computers Kerima Bilal 1st Sept 1st Sept
2 Remove existing computers Ana Ebrahim 2nd Sept 3rd Sept
3 Install new computers Tizita Mitiku 4th Sept 9th Sept
4 Test new computers Sorecha Chala 10th Sept 14th Sept
5 Restore files to new computers Eyob Girma 15th Sept 15th Sept
Milestones
Milestones are established points in the project used to determine whether or not the project will meet the anticipated
schedule. These are usually major events in the course of the project such as ‘installing new computers’ or ‘software
purchased’.
It is important to establish milestones in your implementation plan and monitor the progress of the implementation on
an ongoing basis. You can also gather project progress reports from implementation team members.
Organisational issues
Any impact on the day-to-day running of the business needs to be identified and planned for. For example the installation
may require that the network not be operational for a period of time. Therefore it should be scheduled for a time when
it will have as minimal an impact as possible, for example, after hours. Sometimes it is difficult to identify downtime
when no one would be affected. In all cases, users who will be affected need to have sufficient warning in terms of days
not hours.
Resistance to technology
Change is often seen as threatening, particularly if it is accompanied by ignorance. People sometimes resist new
technology, especially if they are comfortable with the existing system. Resistance can occur at any time however.
Consider an employee who has been transferred to another section where they are not familiar with the technology.
Resistance needs to be addressed, as its negativity can spread to other users and this can adversely impact on the
productivity of the system.
Resistance to technology can often be countered by providing information. Describing the technology, the advantages,
the objectives and other issues to the users can dispel resistance.
User competence
Training and user support are very important. Without this, you may as well not install the new technology because the
benefit it was intended to bring will not be realised. Not only does training need to occur when the technology is first
installed but it has to be provided on an ongoing basis according to need. Part of the continuing management function
is to analyse the skills users require and ensure that they have them.
Not only do users need to be competent in their use of technology but they need to be well supported in its use as well.
The help desk is an important support tool. Its effectiveness relies upon it being continually monitored.
Reflect
Think of a time when you felt apprehensive about using some new technology. What could have been done to make you
less apprehensive about using it?
Feedback
You probably would have appreciated a training session that showed you how to use the technology by applying it to a
familiar problem.
Converting data
A key ingredient of the success of the implementation of new technology is the seamless accessing of data. At some
point the new technology will replace the existing technology (unless there was nothing prior). This usually involves a
conversion process of some kind. The conversion process should ensure that:
• the data is complete and valid
• the structural integrity of both the legacy system and the new database/data warehouse is sound
• the data reflects and works with the business rules and data standards
• the data will work well with the conversion process.
There are four well-recognised methods of system conversion:
1 direct conversion
2 parallel conversion
3 phase-in conversion
4 pilot conversion.
Types of conversion
1. Direct conversion
This is the implementation of the new system and the immediate discontinuance of the old system. Once the conversion
is made there is no way of going back to the old system. It is inexpensive, but involves a high risk of failure because the
entire system is converted at once and going back to the old system will create a lot of hassle and problems.
This approach is appropriate when:
• the system is not replacing any other system
• the old system is judged to be without value
• the new system is either very small or simple, or both
• the design of the new system is drastically different from that of the old system and comparisons between
systems would be meaningless.
2. Parallel conversion
This is an approach where both the old and the new system operate simultaneously for some period of time until a
thorough evaluation is completed. It is the opposite of direct conversion. A high degree of protection from system failure
is provided, but parallel conversion is costly. Usually though, if this conversion type fits in with the organisation’s IT
plan then the extra expense is warranted.
3. Phase-in conversion
This approach allows for a segmented system to be gradually implemented over time until the old system is fully
replaced. Unlike direct or parallel conversion, phase-in conversion uses a step-by-step process of converting one
• administrative benefits
• advanced communications
• customer responsiveness and business enhancement
• innovation, continuous improvement
• employee job satisfaction.
Introduction of new technology may sometimes have adverse effects as well, so the strategy is to ensure that the benefits
outweigh the costs of introducing the new technology. Some of the well-known adverse conditions are: difficulty in
managing the new technology implementations, steep learning curve for gaining new skills, high initial costs, disruptions
to day-to-day routines of the business and excessive time requirements.
OH&S implications
The implementation of new technology may sometimes change the occupational health and safety (OH&S) conditions
in the workplace. Any new technology that is purchased must be assessed against the compliance requirements of
occupational health and safety standards. The rigour of assessment will depend on the complexity and the novelty of the
technology.
Using feedback
The value of feedback
Feedback is extremely valuable in the evaluation of hardware and software as it provides an effective balance for your
own observations and walkthroughs on the system. This is an ongoing process of keeping IT professionals informed of
the performance and usability of the system and should not be treated as merely an event.
While positive feedback reinforces the implementation of the system, negative feedback provides very valuable
information about how to improve the usability and the performance of the system. The performance improvements
made due to the feedback will ultimately benefit the organisation.
Gathering feedback
The goal of collecting feedback from users and gathering information from other sources is to enable the technology
committee to assess how well the software and hardware implementation is satisfying the key usability and performance
indicators.
Sources of information
You can gather data from people, documents, performance data, observation of events or any other empirical method
such as experiments and benchmarking.
Basic feedback gathering methods
The ideal form of feedback gathering is to use a combination of the following methods depending on time and
organisational factors.
Observations, walkthroughs and site visits
These are conducted to get firsthand information on performance and usability features of the system. The internal or
external evaluators will observe all stakeholders using the technology and observe usability and performance indicators
of the system.
Walkthroughs are conducted where an evaluator walks through a certain feature to assess how the system performs that
feature with respect to usability and performance indicators.
Interviews
Here are some tips for conducting interviews:
• Choose stakeholders who would have greater or unique involvement with the new system.
• Communicate the purpose of the interview to the interviewee.
• Ask brief questions relevant to performance and usability of the system.
• Don’t interrupt.
• Be a good listener.
• Take notes.