In the RETT team, we are dedicated at helping Enterprise Modernization customers make the jump of taking out their legacy tools and ease their switch for an IBM Rational-based solution. With a special focus on adoptions of Rational Team Concert Enterprise Extensions (RTC EE).
A customer classification… (to be cont’ed)
Customers we assist are likely to have a DECADE-long history in mainframe development and… a LOT of legacy source code to migrate to RTC EE SCM. But wait a second ! This does not always hold true, especially in the Emerging Markets.
A recent business trip I made to China proved it. We met with financial customers who were NEW to mainframe (note: I’ve already shared some lessons-learned about this trip in the previous blog posts: 1, 2). Not a surprising choice as mainframes have evolved along the way while constantly proving their unique value, performance, level of services, etc. Between us, what other technology could compete with this now turning 50 years old success story ?
Be customers either long time engaged or “new to mainframe”, our sales and Client Technical Representatives (CTPs) face questions about the business added-value and the associated return over investment (ROI) coming with the adoption of the Rational solution. Fair enough. So what is the answer here ?
A sound approach is to map the customer classification given above to ROIs with different scopes:
… for guiding ROI content and scope.
- For a customer bringing new IBM Rational mainframe capabilities into his existing development environment: the ROI should consider productivity, speed, quality, etc.
- For a customer considering taking out a previous tooling (e.g. a tier SCM tool or an existing collaboration tool, …): we should compare apples and apples. Some key indicators about the tier provided solution should be captured and compared with the new ones and a consolidation should be built on top of this exercise. While making explicit the strength of Rational products (our value proposition).
Well, the good news is that IBM Rational provides a number of such ROI tools for ALM, DevOps, Quality & Requirements and… Enterprise Modernization.
Please note that you could find a complete list of them in the References section below.
First, let’s start by CLM in general:
Now, let’s cover the Rational EM tools:
What about RTC EE ?
RTC EE provides additional capabilities to RTC for developing and building mainframe programs with a modern IDE. The ISPF client capabilities let you work with green screens if this is a preferred approach. It provides competitive z SCM tools hosting your z source code and, thing to note, wherever you want (see a previous blog post). As building programs on the System z platform can be expensive (per MIPS and time consumption, etc.), it provides some dependency build, promotion (without rebuilding) and deployment mechanisms.
Traditional benefits from RTC EE adoption include:
- improved compliance and auditability
- decommissioned legacy SCM systems for mainframe & distributed
- unification of practices, removal of redundancies
- improved follow-up on project statuses
- diminished time for rewriting documentation
- improved workflows creation and updates,
For examples of returns on adoptions of RTC EE by Enterprise customers, you could refer to:
Going even beyond about YOUR expected ROI…
Let’s take a step back and discuss the statement, tools and reports provided above. OK. They give you sound estimates. Good enough. As always, the particular context of your company could impact these figures. If you’re looking for the finest-grain ROI and you are in the process of rolling out the Rational solution, one advice here: you would consider including this exercise to be part of a post-pilot activity.
And… what if you add Requirements and/or Test in this picture ?
Needs for testing makes no exception for Enterprise Modernization customers.
From a general standpoint and once the initial learning curve of a test automation tool is passed, test design effort for an automated test is generally considered slightly more expensive than a manual test (30 to 40 % rates are commonly cited). But the payback occurs when tests are automatically replayed (in a quicker way, with no human errors, possibly at night, etc). This is particularly the case for tests run frequently (e.g. for regression testing). You should not minimize the cost of their maintenance though.
The corresponding information for Rational Quality Manager (RQM), Rational Requirement Composer (RRC), Doors, Rational Functional Tester (RFT), … is listed in the table below:
|Quality management (RQM, RRC, Doors, DNG, RFT, etc.)