Lecture 8 - Trust during implementation, Abstract systems Flashcards
What are the 4 stages in an ERP life cycle? (slides)
- Chargering (Decision defining the business case and solution constraints)
- Project (Getting the system and end users up and running)
- Shakedown (Stabilizing, eliminating “bugs”, getting to normal operations)
- Onward and upward (Maintaining systems, supporting users, getting results, upgrading, system extensions)
What is the overall meaning of trust in relation to implementation? (Slides, Defineret i et af Bjarnes studier)
Trust is actors belief in the successful completion of the implementation project. (Slides)
Til hvilke fire elementer snakker vi om trust relationer? (Slides)
People, technology, organisations and social systems.
What is the three levels of trus-based according to Lewicki and Bunker, and what is the conclusion about them? (Schlicther, 2010a)
- People-based trust (“to keep one’s word)
- Knowledge-based trust (“based on predictability - relies on information”)
- Identification-based trust (“the parties effectively understand and appreciate other people’s wants - act for each other”
Conclusion: Development of trust at one level enables lthe development of trust at the next higher level; a violation of trust can also reduce the level of trust, and therefore also change the mechanisms used to develop trust.
(Schlicther, 2010a)
What are the two types of abstract system presented by Giddens? (Schlicther, 2010b)
- Symbolic tokens (a medium that can be passed around among people and groups of people, where these groups can act on the basis of these media in principle, without taking into consideration the specific characteristics of that group. An example is money)
- Expert systems: More complex systems based on, or formed from, a combination of technical means, procedures, professionals expertise and other structures, as for example transport systems. (Schlicther, 2010b)
Abstract systems only work if… (Schlicther, 2010b)
… people trust the system. This means that people need to have faith in the system, so they will use the system, without it being a requirement that they have fully understood how the system is constructed or how it works. (Schlicther, 2010b)
Explain the concepts of technology, rules and actors related to abstract systems through the example of the car transportaion system. (Schlicther, 2010b)
Technology: Cars and roads
Rules: Traffic laws and norms
Actors: Drivers, police and mechanics
(Schlicther, 2010b)
What are the two types of access point to an abstract system?
(Schlicther, 2010b)
- Faceless interaction: You do not meet a real person. Example: withdrawing money from a cash machine.
- Face work interaction: The indicvidual meet a real living person: an expert. Example: withdrawing money from a clerk inside a bank.
(Schlicther, 2010b)
Explain the concept of variance theory and the three conditions provided by Zucker. (related to trust)(Schlichter, 2010b (phd))
Variance theories show the one-directional invariant relationship between cause and effect, between independent and dependent variables. An example o a variance theory is the claim by Zucker that (the level of) trust is dependent on a set of conditions:
- The process itself, e.g. the degree to which a supplier delivers as expected. (process based)
- Those involved share understanding based on gender, culture, race etc., and shared reference frame. (characteristic based)
- Professional standards certifications based on formal structures such as certification, regulation or independent intermediaries (institution based)
Describe the concept of process relations, and the three-stage process model (related to trust) (Schlichter, 2010b (phd)).
Process relations show how trust is developed through a chain of incidents, thus undergoing a change of state; named process theories.
Three-stage process model:
1. People based trust (to keep one’s word). No shared history.
2. Knowledge based trust (based on predictability - relies on information). Fælles historie men ingen tydeligt delte værdier. Eksempelvis
3. Identification based trust (The parties effectively understand and appreciate other people’s wants - act for each other) There is a shared history and paties are interlinked.
Describe the dynamic theories about trust (Schlichter, 2010b - findings) and google docs notes
Both conditions and trust are interrelated. (Bjarne)
Structuration theory provides a ‘dynamic conceptualization of structure as being continuously produced and reproduced through situated practice which facilitates the study of change (Docs notes)
Hvad er de tre phaser i Aladwani, 2001 framework til sikring af success change management ved ERP-implementering? (Change management strategies til at imødekomme resistance to change )
- Knowledge formulation phase: Identify and and evaluate the attitudes of individual users and influential groups of the IT system.
- Strategy implementation: Use the knowledge from phase one to come up with strategies (communication, vis hvordan de kan skabe værdi for den enkelte, training etc.) to avoid resistance to change and implement them.
- Status evaluation phase: Use a performance system to measure ERP implementation status to provide top management with usefull feedback about the degree of resistance to change. I the feedback is very negative it can an opportunity to begin ones again from phase 1.
(Aladwani, 2001)
What is the purpose of the design-gap model? (Heeks, 2006)
So far this design-reality gap model has been used mainly just as an evaluation tool describing failure with its reasons. It is also encouraged to use it as a risk assessment tool when making predictions.
(Heeks, 2006)
In what way can hybrids help to prevent information system failures? (Heeks, 2006)
Hybrids are people with technical as well as other skills (the second skill can be management or medical specific). By involving hybrids in the system design process you can build a bridge between users and developers and help to balance different views and interests and warn about changes in realities that might influence the process and thereby significantly shape a successful outcome of the system design.(Heeks, 2006)
What are the categories of failure of HIS (Health Information Systems) Initiatives described in the article and how many projects fall into which category? (Heeks, 2006)
The first category is total failure, when nothing is implemented in the end (20-25%). The second category is partial failure, which occurs when core objectives are never realized (33-60%). A HIS project is considered a success when the goals of most stakeholders are met (rest: minority of projects).(Heeks, 2006)