Download presentation
Presentation is loading. Please wait.
Published byKimberly Samantha McGee Modified over 8 years ago
1
Robin R. Macfarlane CEO, RRMac Associates 2015 RRMac Associates, LLC
2
Company founded in 2005. Expertise in SCM implementations, conversions, and customizations. Experts in IBM’s CLM Suite (RTC, RDZ, RAA, RD&T) IBM’s Migration Utility (Convert Easytreve to COBOL) Serena’s ChangeMan/ZMF, Dimensions, Business Manager, SSM, Comparex, PVCS CA-Endevor, CA-Harvest ISPW Subversion EzSource Implemented or converted 150+ SCM solutions. ©2015 RRMac Associates, LLC
3
Driving factors No standardization between development groups. Most SCM methodologies were implemented in the late 80’s, 90’s. Lots of manual intervention and interfaces. Audit trail is not consistent. Increased cost for maintenance and process. Relationship with vendor. Current implementations require multiple tools to manage artifacts. Collaboration is clumsy and difficult to manage. Expertise is retiring. ©2015 RRMac Associates, LLC
4
Applications are integrated across multiple platforms. Development teams need integrated tools for collaborative development. Coordinated deploy is now critical. Need to attract new talent. Modern tools with robust IDEs are key. Interactive debugger Language syntax checker Developers working on both mainframe and distributed Re-engineering current solution more costly than a total replacement of tools. ©2015 RRMac Associates, LLC
5
“If it ain’t broke, Don’t fix it” We’ve been doing it this way for years. People are reluctant to change. Our developers will hate it. It will cost too much to convert. Limited time/staff. Homegrown complexity cannot be supported in a new SCM tool. Too many processes will need to change. SCM software bundled with complex maintenance financial offerings. ©2015 RRMac Associates, LLC
6
Phased Approach Pilot Migration using a small, medium and large application. Mixed complexity. Best results are if you choose groups that are champions of change. Implement process improvement and automation when possible. Eliminate obsolete process and technologies. Rip and Replace Need to “beat the clock” on maintenance renewal on current products. Current software doesn’t support new technologies on horizon. Analysis and configuration done up front and then conversion of files done over a weekend or within a short timespan. ©2015 RRMac Associates, LLC
7
Analyze the current process. Critical functions vs. obsolete? Day in the life? What groups are involved? Frequency of changes? SCM Analysis What functions does your current SCM provide? Existing customizations? How are compiles done? Compile options? Versions? Binds, Newcopy? Promotes and Deploys? Proprietary formats and vended code? ©2015 RRMac Associates, LLC
8
Application Analysis What is an application in your environment? Identify all the artifacts/components/elements/files. Are there shared files? Shared libraries? Who owns the code? Do you have all the source? Do you have all the loads? Vendor package. Do you modify any of the code? What gets migrated Files (Source, Copybooks, JCL, PROCs, Control Cards, Link Control, Documentation, Bind Cards, Forms, etc.) Compile options Level zero, archive the older versions ©2015 RRMac Associates, LLC
9
Executive sponsor to help drive the message. Helps keep the project moving. Process improvement should be a key deliverable. Solicit input from your users. Their support is key to success. The Users of the tools and processes have a perspective that you can miss as Administrators of the tools and processes. Understand the new SCM’s architecture. It is different than what your mainframe developers use today. Promote the modern interface and development strengths. Success stories help ease the concerns. Keep it simple. You can add functions later. Avoid GIGO. Now is the time to clean up, time permitting. ©2015 RRMac Associates, LLC
10
Speed up the conversion time and reduce Reduce the cost of the conversion. Process large volumes of data in seconds. Reduce configuration “administrivia” Reduce the impact on your staff. Take the guesswork out of organizing your application files. Help with compiler upgrades. Several customers going to the new compiler as part of the migration. Migrate files, options, history, versions, etc. Generate new SCM Import data Proven technology, automated and repeatable routines. ©2015 RRMac Associates, LLC
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.