Migrating To OpenOffice .org


Published on

Migrating to OpenOffice step by step

Published in: Technology
No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Migrating To OpenOffice .org

  1. 1. Commercial Open Source Software: Migrations <ul><li>OpenOffice.org Migration </li></ul><ul><li>Roberto Galoppini </li></ul>
  2. 2. Visual Agenda
  3. 3. Reasons to change
  4. 4. False problems
  5. 5. Communication
  6. 6. Outsiders matter
  7. 7. No big-bang, please..
  8. 8. Reasons to change <ul><li>Among top reasons to change: </li></ul><ul><ul><li>Technical motivations </li></ul></ul><ul><ul><li>Legal motivations </li></ul></ul><ul><ul><li>Economical motivations </li></ul></ul><ul><ul><li>Social motivations </li></ul></ul>
  9. 9. “Supposed problems” <ul><li>Migrations involving end-users are not just a technical issue. Literature about OpenOffice.org migrations often mentions the following “problems”: </li></ul><ul><ul><li>Functions are “missing” (read they are somewhere) </li></ul></ul><ul><ul><li>OpenOffice Data format (ODF) are not spread </li></ul></ul><ul><ul><li>Layout differences </li></ul></ul><ul><ul><li>There is no documentation ( see amazon ) </li></ul></ul><ul><ul><li>There is no (commercial) support </li></ul></ul>
  10. 10. Issues to be addressed <ul><li>Migrations are never for free: </li></ul><ul><ul><li>Technological impact </li></ul></ul><ul><ul><ul><li>Managing formats & interoperability (R/W/RW patterns) ‏ </li></ul></ul></ul><ul><ul><ul><li>Documents’ Conversion </li></ul></ul></ul><ul><ul><ul><li>Interoperability issues </li></ul></ul></ul><ul><ul><li>Psychological impact </li></ul></ul><ul><ul><ul><li>Need to learn to use a new tool ( what about office 2007 ?) </li></ul></ul></ul><ul><ul><ul><li>Motivational issues </li></ul></ul></ul><ul><ul><ul><li>Inertia to change </li></ul></ul></ul><ul><ul><ul><li>Frustraction </li></ul></ul></ul>
  11. 11. Migration project GANTT Analysis Deployment Training Support and Maintenance Uninstall MS Office Model Migration Comunication
  12. 12. Analysis <ul><li>Analysis is aimed at addressing the following issues: </li></ul><ul><ul><li>Organizational Assessment (Identify Decision makers, Organizational Units, etc) </li></ul></ul><ul><ul><li>Document walk-through (automatic, sampling, pattern r/w/rw, legal aspects) </li></ul></ul><ul><ul><li>Hardware/Software survey (compatibility, needed functions, architecture review) ‏ </li></ul></ul><ul><li>Goals: </li></ul><ul><ul><li>Define a ready-to-go project </li></ul></ul><ul><ul><ul><li>Pilot plan definition </li></ul></ul></ul><ul><ul><ul><li>Migration guide-line definition </li></ul></ul></ul>
  13. 13. Analysis :: Organizational Assessment <ul><li>Goals: </li></ul><ul><ul><li>Identify homogenous class of users </li></ul></ul><ul><ul><li>Identify organizational units responsibles </li></ul></ul><ul><ul><li>Find technological leaders (“champions”) ‏ </li></ul></ul><ul><ul><li>Understand interchange of data among O.U. </li></ul></ul><ul><ul><li>Understand external interchange of data </li></ul></ul>
  14. 14. Analysis :: Documents’ walkthrough <ul><li>Documents’ walkthrough will help to: </li></ul><ul><ul><li>Evaluate issues related to documents' formats </li></ul></ul><ul><ul><li>Templates evaluation and (re) definition </li></ul></ul><ul><ul><li>Identify best training patterns </li></ul></ul>
  15. 15. Analysis :: Data collection <ul><li>Questionnaires will gather information to understand: </li></ul><ul><ul><li>Microsoft office’s mode of employ </li></ul></ul><ul><ul><li>Numbers and categories of documents </li></ul></ul><ul><ul><li>“Critical” documents </li></ul></ul><ul><ul><li>Investigate Internal/External interoperability </li></ul></ul>
  16. 16. Analysis :: Choices <ul><li>At the end of the analysis some choices are needed: </li></ul><ul><ul><li>Define migration target (expectations/budget trade-off, good-will, etc) </li></ul></ul><ul><ul><li>Manage Critical issues (requirements coverage assessment: make/buy/redefine) </li></ul></ul><ul><ul><li>Tools selections (Open Source if possible, of course!) </li></ul></ul><ul><ul><li>Define Support required (related to dimensions, users clustering, statistics) </li></ul></ul>
  17. 17. Communication <ul><li>It is mandatory, and it requires: </li></ul><ul><ul><li>Top Management commitment </li></ul></ul><ul><ul><li>Trade Unions commitment </li></ul></ul><ul><ul><li>“Champions” commitment </li></ul></ul><ul><ul><li>Internal Marketing (motivational training) </li></ul></ul>
  18. 18. Communication :: Internal Marketing <ul><li>It consists of: </li></ul><ul><ul><li>Portal (intranet with wikis, blogs, etc) ‏ </li></ul></ul><ul><ul><li>Software Customization (personalised version of OOo) </li></ul></ul><ul><ul><li>Software distribution (also outside of the company!) </li></ul></ul><ul><ul><li>Stimulate “peer learning” (champions’ role is key!) </li></ul></ul><ul><ul><li>Keep people informed, about processes and tools </li></ul></ul>
  19. 19. Documents and Templates Migration <ul><li>It could be easier than expected: </li></ul><ul><ul><li>It is an organizational opportunity (templates, flows, etc)! </li></ul></ul><ul><ul><li>Document management opportunity (file servers, etc) </li></ul></ul><ul><ul><li>Archiving “old” documents as read-only (don’t need to migrate all of them!) </li></ul></ul>
  20. 20. Deployment <ul><li>Installation and configuration. </li></ul><ul><ul><li>Customized installation </li></ul></ul><ul><ul><li>“Critical” workstations availability (you likely need them!) </li></ul></ul><ul><ul><li>Extensions’ attribution </li></ul></ul><ul><ul><li>Move to new formats (burn the boats!) </li></ul></ul>
  21. 21. Deployment :: (Dis)installation <ul><li>The migration will take place step by step (big-bang simply doesn’t work) . </li></ul><ul><li>At a certain date it must be effective . </li></ul><ul><li>Only where and if necessary some desktops will stay . </li></ul>
  22. 22. Training <ul><li>Is the most visible activity. </li></ul><ul><ul><li>Motivational, especially for responsibles and champions </li></ul></ul><ul><ul><li>Advanced for Champions and call center operators </li></ul></ul><ul><ul><li>Educate everyone about interoperability issues </li></ul></ul><ul><ul><li>Differentiated, from basic to very advanced </li></ul></ul><ul><ul><li>Training program should consider second editions </li></ul></ul>
  23. 23. Maintenance and Support <ul><li>Help users with technical and not technical problems. Never let them alone.. </li></ul><ul><ul><li>Zero level support: intranet (documentation, how-to, faq, news, wiki, etc) ‏ </li></ul></ul><ul><ul><li>Peer support and champions support </li></ul></ul><ul><ul><li>First level support: call center </li></ul></ul><ul><ul><li>Second level support: (phone and/or on-site) ‏ </li></ul></ul><ul><li>The portal plays a very important role here.. </li></ul>
  24. 24. Conclusions <ul><li>A migration is a process, not a tool. </li></ul><ul><ul><li>Don’t underestimate Psychological impact of change </li></ul></ul><ul><ul><li>Don’t leave them alone, never </li></ul></ul><ul><ul><li>Motivate through speeches, help on a practical ground </li></ul></ul><ul><ul><li>Training and support are key </li></ul></ul><ul><ul><li>Users need answer, fast! </li></ul></ul>
  25. 25. Anteprima a OpenOffice.org 2.0 Thank you! Roberto Galoppini http://robertogaloppini.net [email_address]