MOST has vast experience in executing end-to-end mainframe and iSeries related projects. Whether the projects are conversion, migration or application maintenance, MOST's project methodology and its' supporting tools form the foundation for executing all phases of the project.
Our methodology is based on best practices that have evolved as a result of conducting many projects. It involves professionals who are experienced in the process, automatic tools, and on-site activities that include interaction with customer SMEs. Tasks that can be done remotely, such as code conversion, are performed off-site and may use MOST's mainframe or relevant open systems platform.
Special attention is paid to the customer's IT standards, procedures and other environmental prerequisites.
It is MOST's practice that at no point in the process is it required to have off site access to production data.
Using this methodology, MOST is able to successfully implement projects on time, on budget and with high quality.
What We Do
MOST project methodology is a structured approach to conducting various types of modernization projects. The methodology is a result of having conducted multiple projects. This methodology is adapted to reflect the specifics of the customer's requirements and project management practices.
The following are common to all projects:
Project management and planning
Modernization projects are of a technical nature requiring strong technical management. At MOST project managers have a combination of both management and technical skills allowing them to get involved in all aspects of the project.
Key to the success of any project is the planning of the project following an assessment and in depth study of the application/s to be modernized. MOST's project manager pays careful attention to the planning phase of the project and the creation of a project plan together with the customer.
Phased delivery reduces project risk. During the assessment MOST evaluates with the customer the option of phased delivery depending on business needs and technical feasibility. Phased delivery may require co-existence between the components that have been converted and those that are yet to be converted. MOST has the experience and the technical knowhow to support such phasing in order to reduce risk.
Risk management is an integral part of MOST project management.
An in depth analysis at the beginning of the project is key to mitigating project risk. This process uses automated tools to identify all components that will comprise the project scope. It also uncovers gaps and issues that need to be resolved prior to advancing to the next phase of the project.
Key to MOST's approach to minimizing risk is to avoid manual intervention in the application modification process. Defects uncovered during testing, for example, will be rectified by modifying the responsible code generator and redelivering the generated code rather than making manual changes to the code.
There is a need to ensure business continuity over the duration of any modernization project. Such continuity includes the ability to maintain and modify existing application/s in response to ongoing business needs. MOST's project methodology and its toolset allow changes to be made to the existing applications in parallel to the process of modernization.
MOST's methodology incorporates testing during all phases of the project. Each deliverable undergoes a testing process relevant to its content.
Modernization projects require the new application and the original application to function in the same way. Therefore MOST's methodology uses the original application as a baseline for testing the converted application. In support of this testing MOST's MF-Test may be used to run multiple testing scenarios, both online and batch
The need for customer involvement is well defined in MOST's methodology and is agreed upon with customer during the planning phase of the project.
The majority of project work is done off site with MOST personnel coming on site at key delivery phases of the project.
MOST activities are conducted without the need to have access to customer's data.
The following diagram illustrates the typical project life cycle.