I need scientific articles about Change Management related to IT Projects?
Dear Vivian Isabel Antúnez Saiz
The methodology of change management related to IT projects often aligns with established frameworks like ITIL (Information Technology Infrastructure Library) or ADKAR (Awareness, Desire, Knowledge, Ability, Reinforcement). These methodologies provide structured approaches for planning, implementing, and managing change in IT environments. ITIL focuses on aligning IT services with business needs, emphasizing continual improvement. ADKAR, on the other hand, centers around individual change, addressing key stages of awareness, desire, knowledge, ability, and reinforcement. Both frameworks offer guidelines and best practices to navigate the complexities of change in IT projects, ensuring successful transitions and stakeholder engagement.
I hope this helps.
I am familiar with two models:
1- TIL (Information Technology Infrastructure Library) is a widely adopted framework for IT Service Management (ITSM) is more into the governance of change.
2- Kotter's 8-Step Change Mode it works for IT and non non IT related projects.
Dear Vivian Isabel Antúnez Saiz,
There are some IT Tools for change management (CM) I've involved during a research previously. Particularly, the research found interconnection between CM and IT tools. It is Knowledge Management. It turns out that during times of change in a company, their knowledge assets are important. Their preservation and the way they are transferred. CM project teams can be such knowledge bases. My paper about this is on its way for publication. Here's an excerpt: “In practice, in CIS enterprises there are single independent ways of introducing knowledge management, mainly among IT companies that share their mistakes, achievements, difficulties within participants at knowledge management conferences. The main tools for the implementation of the company are software - the Confluence knowledge data base, and the Jira data base and others, which are extremely rare among non-IT enterprises.” In fact, these IT tools – Confluence, Jira, bases on Kanban, Lean which is good practice in IT world itself.
Balanced Scorecard, Cynefin, SenseMaker (https://cynefin.io/wiki/Main_Page)
The Change Management planning generally adopts the Change Acceleration Process framework, a model developed by General Electric which is relatively similar to John Kotter's 8-Step Change Model, which outlines the following seven aspects of changes:
1. Leading Change
2. Creating a Shared Need
3. Shaping a Vision
4. Mobilizing Commitment
5. Making Change Last
6. Monitoring Progress
7. Change Systems and Structures
As per this methodology, various Change Management instruments (tools) are specified for the project, and these tools are associated with the mentioned aspects. The second key element of the methodology involves analyzing stakeholders and assessing their potential attitudes. Stakeholders, whether internal or external to the organization/institution, are individuals or groups impacted by the project and are categorized based on common status, interests, and power within the organization. Finally, the third major component of the methodology encompasses a range of potential Change Management instruments, such as communication, training, involvement, motivation, control, etc.
- Badges
- Science topic
- Similar topics
- Biological Science
- Zoology
- Ornithology
- birds
- Scopus