ISD Lecture 4 From systems development to technochange Flashcards
Describe Technochange project
A project that changes an organization based on new uses of IT.
Using IT in ways that can trigger major organizational changes creates high-risk, potentially high-reward, situations that Markus call technochange: technology-driven organizational change. Today these project would be labelled as “transformational” or “disruptive”.
Technochange differs from typical IT projects and typical organizational change programs and requires a different approach.
The classic mistake is to manage a Technochange project as an IT project simply because the organization have failed to understand that it actually was a Technochange project.
Describe IT project
A purely technical IT project (such as upgrading a web-server).
Organizations can do many useful and valuable things with IT other than changing organizational activities and performance results.
Technical and economic benefits can be had through simple upgrades and technology substitutions that do not require much effort on the part of business users.
For example upgrading a departmental web server: it all goes well, it happens overnight and if users notice at all they enjoy better response time.
Problems of separation
The problems that comes from separating IT development from organizational development.
The root cause for many Technochange problems is too much separation between systems development and implementation – between IT and organization.
For example
We might have one project – e.g. using XP – to deliver a software solution, and another project responsible for implementing the software.
We might have one project done by a vendor delivering software to a customer organization, and have an implementation project in the customer organization being responsible for implementation.
A complete design
A design that not only consist of the design of an IT systems but also the design of the changes to the organization.
A design that is implementable
A design without misfits towards key organizational characteristics such as the culture, business process and incentives.
The second condition for a successful technochange is a solution that can be, and is, adopted and used.
Technochange prototyping
An iterative approach that not only focus on the development of IT, but the organizational changes and benefits as well.
One solution, to address separation problems, is to use Technochange prototyping.
Technochange prototyping is iterative / agile development + organizational changes integrated into one, and the same, process.
The essential characteristic of the Technochange prototyping approach is that each phase (iteration) involves both new IT functionality and related organizational changes, such as redesigned business processes, new performance metrics, and training.
Benefits realization
the process of organizing and managing, such that the potential benefits arising from the use of IT are actually realized.
Benefits realization provides another, but similar, way of addressing separation problems and achieving business value.
The paper claims that some of these problems might be solved if organizations use benefits realization defined as: the process of organizing and managing, such that the potential benefits arising from the use of IT are actually realized.
By combining these ideas with the ideas from technochange organizations might be in a better positions to successfully manage IS development and implementation projects.
Benefits realization model
Benefits planning
Benefits delivery
Benefits review
Benefits exploitation
What is benefits planning
Benefits do not simply emerge, as if by magic, from the introduction of a new technology.
Their realization needs to be carefully planned and managed.
the ability to effectively identify and enumerate the planned outcomes of an IS development project and explicitly stipulate the means by which they will be achieved.
What is benefits delivery
Consequently, organizations will only be able to deliver value from their IT investments if they can develop a benefits delivery competence, which the paper define as: ‘
the ability to design and execute the programme of organizational change necessary to realize all of the benefits specified in the benefits realization plan.
What is benefits review
The benefits from IT investments will only be realized if they are measured and managed in a systematic way.
Organizations must, therefore, be able to effectively monitor and evaluate the results of their projects, on an on-going basis, to ensure that its ability to deliver business value is incrementally improved.
Consequently, the benefits review competence can be defined as:
the organization’s ability to effectively assess the success of a project in terms of the potential benefits, the delivered benefits, and the identification of the ways and means by which further benefits might be realized.
What is benefits explotation
It is often the case that the full potential of a particular application does not become apparent until it is fully operational and the stakeholder community has become experienced in its use.
In this respect, the ability to work with information is particularly crucial.
It is therefore necessary for organizations to develop and apply a benefits exploitation competence, which can be defined as
The adoption of the portfolio of practices required to realize the potential benefits from information, applications and IT services, over their operational life.
Problems with Classic IT Project Management
do typically not address the major risk in technochange: that people will not use IT and related work practices. The focus is on project cost, project schedule, and system functionality.
Although the discipline of project management is a very important contributor to successful technochange, it has very little to say about how to manage the risks associated with people’s ‘resistance to change’.
Problems with Classic IT Project Management + Organizational Development
to much separation.
Bad technochange
Technochange solutions can be bad in two major and related ways:
• They can be incomplete,
• and they can be misaligned with the organization.
Technochange projects should change organizations – but in ways that are implementable.