1 / 10

Strategic Software Installation Planning for Organizational Success

Learn about the complexities and risks involved in installing new software in an organization. Explore strategies for migration, addressing both technical and organizational aspects. Plan systematically, manage change effectively, and ensure support and maintenance for a successful transition.

basil-black
Download Presentation

Strategic Software Installation Planning for Organizational Success

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Installation (ch. 15) MSO 08/09, WP

  2. Issue • It is about the final step of “installing” a new software in an organization. • The issue is not just about the software itself. The whole organization has to change along as well! • Which makes ‘installation’ complex and risky you need to handle this systematically! (have a plan)

  3. Global strategy Current System New System migration Unfreeze • Refreeze • Support • Maintenance • Technical conversion • Change ‘management’ Plan these out in a ‘migration plan’ !

  4. “Conversion” • Address the technical aspect of migration, covering: • Install (new) hardware • Install (new) software • Converting old business data • Strategies: parallel modular whole system direct simultant pilot phased Note that the strategies are ordered differently than in the book !

  5. Risk & Cost parallel modular whole system direct simultant pilot phased • In this pic. the strategies are ordered such that: • Time and cost increase along any dimension. • Risk decrease along any dimension.

  6. Change ‘management’ • Address the organizational aspect of migration (the organization has to migrate as well), covering: • Revising work procedures & policies • Training • Assessing cost/benefit • Motivating adoption of new systems • Important to realize that there are three parties here: • Change sponsors  within organization, have authority • Change agent  just the project management body, has no authority • Adopters / users  people that must adapt to the new system • may make costly mistake (imporper training etc) • may resist

  7. Refreeze / post-implementation activities Current System New System migration • Refreeze • Support • Maintenance

  8. System support • Is defined as: support for helping users to use the system (Dennis et al). • On-line support: FAQ, wiki, message board, etc. • Help desk

  9. System Maintenance • Is defined as: the process of refining the system to make sure it continues to meet business need (Dennis et al). This includes: • Fixing bugs. • Modification (small or large): • Changing or improving existing features. • Adding new features. • In many cases the maintenance cost is actually bigger than development cost.

  10. Finally ... • You have seen it all ....Now go and make your software project! • Remember all what you have learned here. Try to apply it at small scale in your SP.You’ll cherish that experience when you latter participate in your real mega-euro project.

More Related