Your SlideShare is downloading. ×
Demystifying the TeamConnect 3.x Upgrade Process
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

Demystifying the TeamConnect 3.x Upgrade Process

923
views

Published on

Demystifying the upgrade process for TeamConnect Enterprise 3.x Legal Matter Management System. Learn how Textron managed their upgrade process and trained attorneys and legal staff on the new …

Demystifying the upgrade process for TeamConnect Enterprise 3.x Legal Matter Management System. Learn how Textron managed their upgrade process and trained attorneys and legal staff on the new version.


0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
923
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
12
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Interact 2010 Demystifying the Upgrade: Practical Considerations to Keep Your System Current © Huron Consulting Services LLC. All rights reserved.
  • 2. Panelists and Facilitators Best Looking Logo g g Director of L Di t f Legal l Gerald Gatt Administration Manager, Legal Maria L M i Leggett tt Business Analysis Michael Stetzer Director Rich Seleznov Managing Director
  • 3. Agenda • Planning • B i C Basic Considerations id ti • Upgrade Objectives • A Approach h • Changes / Challenges • Testing • Training • Success Factors • Tools • Questions and Answers 3
  • 4. Planning Process g The planning process is critical to the overall success of g your project. You should include representatives from your IT group, Mitratech, Legal and partner or 3rd party service provider during the initial phase of the project project. 4
  • 5. Assembling the Team g • IT Group – Will help provide resources to meet your project schedule – Should review dependencies with versions of hardware and software components: • W b Server, Application Server, Database Web S A li ti S D t b – May be required to assist with installation, backup and cut-over activities • Mitratech – Can provide access to relevant source code – May assist with remediation estimates and remediation activities – May provide warranty or support for any potential upgrade issues 5
  • 6. Assembling the Team g • Service Provider – Knowledge on upgrade specifics and process – Remediation activities and estimates – Project management – Training and support • Legal Business Area – Knowledge of current design – Assess impact to the users – Participation in testing, training, communications with end users 6
  • 7. Demystifying the Upgrade – y y g pg Basic Considerations • Why should I upgrade? • How much will it cost? • How long will it take? • What is the impact to my organization? • H How d I get started? do t t t d? 7
  • 8. Demystifying the Upgrade – Why should I upgrade? • Compliance and compatibility p p y – Hardware / Software • Support & Maintenance – Bug fixes / Patches g – Required • Leverage New Features – Searching – Performance enhancement – Usability • Improve Productivity • Redesign • Business Process Improvement Opportunities 8
  • 9. Answer to Remaining Questions It all depends….. depends on your specific y p needs Cost? Time? Impact? 9
  • 10. Demystifying the Upgrade – Basic Considerations • How much will it cost? $50,000 to $125,000* $ , $ , • How long will it take? 3-months to 6-months* • Impact to the organization? Minor to Moderate There is no one answer to these questions because of q dependencies. *cost and time estimates are based on assumptions and experience from upgrading clients from version 2.4 to 3.1. p p pg g 10
  • 11. Demystifying the Upgrade – Dependencies • Who is doing the work? • Internal, Partner Service Provider, Mitratech • Are internal resources able to work on this initiative? •HHow extensive h t i have you customized th d i ? t i d the design? • CJB, Java Script, Tools • Do you have add-on components or integrations? • Are your end users comfortable with the system or do they need a lot of training? 11
  • 12. Demystifying the Upgrade – Upgrade Objectives Common Objectives • Upgrade TeamConnect • Resolve and remediate any application components • Test the new version, features, and any remediated application components • Resolve any defects • Train staff on new features and any design or user interface y g changes • Deploy the TeamConnect upgrade into production * Complete all objectives without jeopardizing business continuity 12
  • 13. Demystifying the Upgrade – Approach Every design is unique The cost, effort and impact for your specific application will be dependent on a number of factors. Th t b i said th approach f th upgrade should That being id the h for the d h ld consider at least two specific phases. Phase 1: Assessment Phase 2: Remediation / Upgrade Implementation 13
  • 14. Phase 1: Assessment – Approach The objective of the Assessment Phase is to understand the impact of your design and to better estimate the effort and cost to complete the upgrade. 14
  • 15. Phase 1: Assessment – Approach Assessment Dependencies Include: • Overall size and complexity of your design • A il bilit and currency of source code Availability d f d • Access to resources familiar with your design • Current version of TeamConnect • Coordination with Mitratech, 3rd Party Service providers and internal staff • Commitment to the planning process • Comprehensive understanding of the upgrade 15
  • 16. Phase 1: Assessment – Approach Activities: • Review release notes, installation guide for TeamConnect version 3.x • Coordinate upgrade activities with IT and other participants • Copy latest version of TeamConnect into a test environment • A l upgrade f Apply d from 2 4 t 2 5 if current version i prior t 2.4 to 2.5 t i is i to 2.4 additional steps may be required • Apply upgrade from 2 5 to 3 1 SP2 2.5 3.1 16
  • 17. Phase 1: Assessment – Approach Activities: • Identify design elements that require remediation • Perform basic testing to verify design and identify potential issues • Work with Mitratech, internal resources and/or partner service provider to assess remediation effort • Develop a remediation plan including estimates and schedule h d l • Determine level of testing required - develop a high level test plan 17
  • 18. Phase 1: Assessment – Approach Activities: • Determine approach for training - develop and training plan • Develop estimates for remediation phase • Develop plan and schedule for remediation phase 18
  • 19. Phase 2: Remediation – Approach The objective of the Remediation Phase is to complete the j p upgrade including any remediation, testing, training and implementation activities. 19
  • 20. Phase 2: Remediation – Approach Remediation dependencies include: p • Number of design elements that require remediation • Work effort estimates • Dependencies with internal resources Mitratech or 3rd resources, Mitratech, party service providers • Testing approach • Full regression, limited system testing • Training approach • Train the trainer, hands-on, Webex, or presentation , , , p • Other dependencies • Hardware or Software upgrades • Enhancements 20
  • 21. Phase 2: Remediation – Approach Activities: • Complete all remediation activities –Modify custom screens / blocks / XML tags / Java code –Search views Search –Home Pages –Wizards • Coordinate remediation work with internal resources, Mitratech and Partner • Install and test remediated design elements 21
  • 22. Phase 2: Remediation – Approach Activities: • Track all remediated application components for deployment • Complete system testing or regression testing including detailed test plan & test cases • Resolve defects • Develop training materials • Schedule & conduct training • Coordinate activities and schedule implementation • Deploy upgrade in production environment 22
  • 23. Changes / Challenges g g 3.1 Upgrade • New API impact to the following design elements –Custom Screens –Java Java –XML –Java script • New Batch Display –Simplified –Based on rows and columns Based –Easier to develop custom screens 23
  • 24. Changes / Challenges g g 3.1 Upgrade • Web Services –Alternative to XML layer now available • Wizards –Parameters and page transitions have been modified •S Search Vi h Views –New search views system created –Object collections j 24
  • 25. Testing g Testing may be required at various levels depending on your organization’s requirements. Your approach to testing should be based on the risk. Critical areas of the system should always be tested with every new product upgrade or release. 25
  • 26. Testing g • Full Regression Testing of complete application and all g g p pp design elements: rules, integrations, wizards, search views, etc.. • Remediation Testing of remediated design elements only • Integration Testing of integration components such as f AP or e-Billing interfaces • Report Testing of reports or reports that may be impacted by database changes • System Testing of key design elements according to overall functions to complete business processes 26
  • 27. Training g Approach will vary depending on y pp y p g your user base and the comfort they have with the current system. Provide materials or demos of the 3.x system to a core 3x group to assess the level of training that will be needed. Limit training to design changes and specific f enhancements. Highlight differences between 2.x version and 3.x. Consider allowing users to login to a test environment and experience the new design prior to the scheduled implementation. 27
  • 28. Training g 3.1 User Interface Enhancements • Gl b l N i ti Global Navigation • Home Page Management • System Administration –Setup (Designer View) –Admin (Users Groups Logs Settings, License file) (Users, Groups, Logs, Settings • Hover (Record Snap Shot) 28
  • 29. Training g 3.1 User Interface Enhancements • S Searching hi –(Look ahead) –Search Collections –Custom Searching • Hyperlinks to Records • Save and Close 29
  • 30. Training Alternatives g • Webex overview – Presentation and demonstration • Training Sessions – Presentation in-person and demonstration only • T i i S Training Sessions with h d i ith hands-on exercises i – Allow users to use the new search features – Create exercises to allow users to create custom searches • Train-the-Trainer – Identify key power users and train them on the new features – Allow these folks to serve as point personnel for questions regarding the new design • Training for System Administrators – Training covers new Setup and Admin options for existing g p p g administrators 30
  • 31. Success Factors • Planning & Communication –Most projects don’t plan to fail but fail to plan Most don t –Let Mitratech and your internal staff know about your plans in advance so everyone is on the same page and available when they are needed –Review latest release notes and know the product release schedule • Partnership –Work with Huron and Mitratech who have experience with this process to reduce risk and improve quality and success of your upgrade 31
  • 32. Success Factors • Network –Utilize your attendance at the conference to make Utilize connections with other clients who have experienced the upgrade –Don’t be afraid to reach out and visit other clients or request a demonstration, live meeting, or conference call • Complete a thorough assessment –Know your current design –Complete a thorough inventory of your design components • Don’t overcomplicate training 32
  • 33. Upgrade Resources pg Use what is available… • 3.x Installation Guide • 3.x Release Notes • Screen Conversion Tool • Database Validation Script • TC Legal Conversion Kit • Getting Ready for TeamConnect 3.x Solution Development Guide (pdf) • Network with your peers 33
  • 34. DTE - Upgrade Status pg Background –DTE went from version 2.4 t version 3 1 SP2 DTE tf i 2 4 to i 3.1 –Assessment was conducted in 2009 and took approximately 1-month to complete pp y p –Implementation was completed in Jan 2010 – entire upgrade completed in 3-months 34
  • 35. DTE - Upgrade Status pg Challenges –LDAP changes LDAP h –eBilling Adapter using the Post Tool and XML integration required testing g q g –Rewrite Time Entry tool and 12 custom screens utilizing the batch display 35
  • 36. DTE - Upgrade Status pg Success Factors –Partner experience with T P t i ith TeamConnect upgrade process C t d and DTE design –Limited scope to only focus on upgrade – no other p y pg changes –Training focus was simplified – Conducted a series overview sessions (1-1 5 hours) (1-1.5 • Hand out materials with new features and changes • Highlight added value not change • T ti did not complete f ll regression only moderate Testing t l t full i l d t system testing in key areas 36
  • 37. DTE - Upgrade Status pg Results –End users have provided very positive f db k on th E d h id d iti feedback the new interface • Like browser option ability to utilize back button p y • Ability to view recent records • New Save options (save & close, save & view) • Ability to create Custom searches 37
  • 38. Textron - Upgrade Status pg Background – Textron is upgrading from 2.5 SP 2 to 3.1 SP1 Update 2 – Began upgrade project in September 2009. Will go live in June 2010. 38
  • 39. Textron - Upgrade Status pg Challenges – Upgraded included server infrastructure upgrade (New Servers, Oracle and WebSphere version updates) – Need to re-code AP interface framework. Current framework not compatible with 3.x – Lots of custom XML screens updates to match 3.x look and feel and JavaScript code had to be updated. – Extensive testing and user training 39
  • 40. Textron - Upgrade Status pg Success Factors – New features of 3.x – easier to navigate, custom searches are helping users embrace the process of upgrading 40
  • 41. Questions and Answers • How long did it take to upgrade? • What were some of the key challenges? • Did you run into any issues? • How did your end users respond to the new features? 41
  • 42. 42