Difference between revisions of "Change Management Considerations"

From ADempiere
Jump to: navigation, search
This Wiki is read-only for reference purposes to avoid broken links.
m (Adding more references)
m (Intermediate save - more to follow.)
 
Line 1: Line 1:
 
Just starting this page.  Check back soon.
 
Just starting this page.  Check back soon.
 +
 +
Nice quotes:
 +
::...there are two fundamental sources of resistance to innovations like an ERP: perceived risk and habit. Perceived risk refers to one’s perception of the risk associated with the decision to adopt the innovation, i.e. the decision to accept an ERP system.[http://pdfcast.org/pdf/change-management-strategies-for-successful-erp-implementation]
 +
::If management wants the new system to be adopted by the users, then users’ adoption costs should be kept to a minimum.[http://pdfcast.org/pdf/change-management-strategies-for-successful-erp-implementation]
  
 
References:
 
References:
* [http://pdfcast.org/pdf/change-management-strategies-for-successful-erp-implementation Change management strategies for successful ERP implementation]
+
# [http://pdfcast.org/pdf/change-management-strategies-for-successful-erp-implementation Change management strategies for successful ERP implementation]
::When implementing an enterprise resource planning (ERP) system, top management commonly faces an unwanted attitude from potential users-for one reason or another, they resist the implementation process. Top management should, therefore, proactively deal with this problem instead of reactively confronting it. This paper describes an integrated, process- oriented approach for facing the complex social problem of workers' resistance to ERP.
+
#:When implementing an enterprise resource planning (ERP) system, top management commonly faces an unwanted attitude from potential users-for one reason or another, they resist the implementation process. Top management should, therefore, proactively deal with this problem instead of reactively confronting it. This paper describes an integrated, process- oriented approach for facing the complex social problem of workers' resistance to ERP.
* [http://www.imamu.edu.sa/Scientific_selections/abstracts/Documents/A%20Critical%20Success%20Factors%20Model%20For%20ERP%20Implementation.pdf A Critical Success Factor Model for ERP Implementation]
+
# [http://www.imamu.edu.sa/Scientific_selections/abstracts/Documents/A%20Critical%20Success%20Factors%20Model%20For%20ERP%20Implementation.pdf A Critical Success Factor Model for ERP Implementation]
::An effective IT infrastructure can support a business vision and strategy; a poor, decentralized one can break a company. More and more companies are turning to off-the-shelf ERP solutions for IT planning and legacy systems management. The authors have developed a framework to help managers successfully plan and implement an ERP project.
+
#:An effective IT infrastructure can support a business vision and strategy; a poor, decentralized one can break a company. More and more companies are turning to off-the-shelf ERP solutions for IT planning and legacy systems management. The authors have developed a framework to help managers successfully plan and implement an ERP project.
* [http://www.entrepreneur.com/tradejournals/article/162620690.html Change management: ensuring success in your ERP implementation]
+
# [http://www.entrepreneur.com/tradejournals/article/162620690.html Change management: ensuring success in your ERP implementation]
* [http://is2.lse.ac.uk/asp/aspecis/20040082.pdf CHANGE MANAGEMENT PERSPECTIVES IN AN ERP IMPLEMENTATION]
+
# [http://is2.lse.ac.uk/asp/aspecis/20040082.pdf CHANGE MANAGEMENT PERSPECTIVES IN AN ERP IMPLEMENTATION]
::This case study analyses a multiyear ERP (SAP R/3) implementation project in a global company from perspectives of conflicts and problems the project faced. The paper reports on the core of the implementation activities from the start of the project in late 1995 until mid 2000, when most of the originally estimated implementation efforts were finished. The study reveals what pitfalls an inappropriate understanding of the magnitude of changes required for implementation involves and what unidentified consequences can result from this. The main reasons for problems encountered are discussed and analysed. The main lesson of the study is that the fundamental challenge of ERP implementations is not technology but organisational and human changes, which, if not properly understood and addressed, can lead to unidentified consequences causing implementation failures.
+
#:This case study analyses a multiyear ERP (SAP R/3) implementation project in a global company from perspectives of conflicts and problems the project faced. The paper reports on the core of the implementation activities from the start of the project in late 1995 until mid 2000, when most of the originally estimated implementation efforts were finished. The study reveals what pitfalls an inappropriate understanding of the magnitude of changes required for implementation involves and what unidentified consequences can result from this. The main reasons for problems encountered are discussed and analysed. The main lesson of the study is that the fundamental challenge of ERP implementations is not technology but organisational and human changes, which, if not properly understood and addressed, can lead to unidentified consequences causing implementation failures.
* [http://www.collegiateproject.com/articles/Navigating%20Organizational%20Change.pdf Navigating Organization Change on an ERP Implementation: A Comprehensive Organization Change Management Plan Can Help Improve Your ERP Project’s Likelihood of Success]
+
# [http://www.collegiateproject.com/articles/Navigating%20Organizational%20Change.pdf Navigating Organization Change on an ERP Implementation: A Comprehensive Organization Change Management Plan Can Help Improve Your ERP Project’s Likelihood of Success]
::Change is inevitable when working on any large project or change initiative – especially with the implementation of an ERP system. Institutions preparing for an ERP implementation should proactively approach and manage change to improve the likelihood of success of the implementation project and the ultimate use of the new system.
+
#:Change is inevitable when working on any large project or change initiative – especially with the implementation of an ERP system. Institutions preparing for an ERP implementation should proactively approach and manage change to improve the likelihood of success of the implementation project and the ultimate use of the new system.

Latest revision as of 05:26, 1 February 2011

Just starting this page. Check back soon.

Nice quotes:

...there are two fundamental sources of resistance to innovations like an ERP: perceived risk and habit. Perceived risk refers to one’s perception of the risk associated with the decision to adopt the innovation, i.e. the decision to accept an ERP system.[1]
If management wants the new system to be adopted by the users, then users’ adoption costs should be kept to a minimum.[2]

References:

  1. Change management strategies for successful ERP implementation
    When implementing an enterprise resource planning (ERP) system, top management commonly faces an unwanted attitude from potential users-for one reason or another, they resist the implementation process. Top management should, therefore, proactively deal with this problem instead of reactively confronting it. This paper describes an integrated, process- oriented approach for facing the complex social problem of workers' resistance to ERP.
  2. A Critical Success Factor Model for ERP Implementation
    An effective IT infrastructure can support a business vision and strategy; a poor, decentralized one can break a company. More and more companies are turning to off-the-shelf ERP solutions for IT planning and legacy systems management. The authors have developed a framework to help managers successfully plan and implement an ERP project.
  3. Change management: ensuring success in your ERP implementation
  4. CHANGE MANAGEMENT PERSPECTIVES IN AN ERP IMPLEMENTATION
    This case study analyses a multiyear ERP (SAP R/3) implementation project in a global company from perspectives of conflicts and problems the project faced. The paper reports on the core of the implementation activities from the start of the project in late 1995 until mid 2000, when most of the originally estimated implementation efforts were finished. The study reveals what pitfalls an inappropriate understanding of the magnitude of changes required for implementation involves and what unidentified consequences can result from this. The main reasons for problems encountered are discussed and analysed. The main lesson of the study is that the fundamental challenge of ERP implementations is not technology but organisational and human changes, which, if not properly understood and addressed, can lead to unidentified consequences causing implementation failures.
  5. Navigating Organization Change on an ERP Implementation: A Comprehensive Organization Change Management Plan Can Help Improve Your ERP Project’s Likelihood of Success
    Change is inevitable when working on any large project or change initiative – especially with the implementation of an ERP system. Institutions preparing for an ERP implementation should proactively approach and manage change to improve the likelihood of success of the implementation project and the ultimate use of the new system.