Ismail E.

General Context:

The project is part of the overall Powersuite2024 strategy and consists of:

• Using a SaaS application: the Bullhorn ATS-CRM solution has been selected.

• Modernization and digitalization of business processes.

• Obsolescence management: Manpower's main business applications for order and temporary staff management are developed on a Flex base that will no longer be supported on browsers.

The Bullhorn solution consists of:

• A web application.

• A mobile web application.

The Bullhorn solution needs to be integrated into the Manpower information system. Therefore, it requires data from the Manpower IS (assignments, payroll, safe, advance, etc.) AND must provide the Manpower IS with necessary information for other functionalities (candidate/temporary staff data for Mission, Payroll, BI, manpower.fr, mobile application, etc.).

This implies data migration to and from Bullhorn. Two solutions have been selected:

• Talend for client and order flows.

• Java for candidate flows.

Project Subject:

CHANGING ERA

Work Performed:

I- Preparation of a test strategy.

II- Presentation and implementation of the test strategy.

III- Analysis Phase

▪ Reading and analysis of SFG and SFD for each flow.

▪ Scheduling meetings with the Business or IT department if more details are needed.

▪ Writing the test plan.

▪ Estimating the time for test design and execution.

IV- Design and Execution Phase

▪ Designing test cases.

▪ Executing tests.

▪ Communicating the test progress percentage.

▪ Creating homologation anomalies if needed.

V- Writing acceptance test reports.

VI- Participation in the continuous integration process (deployment, configuration modification).

General Context:

The IT department's testing unit assigns requests to the CDS; each team member handles one or more requests, depending on their workload and level of expertise on the subject(s).

Project Subject:

- Lead the activity of a team of 4 homologators.

- Homologate one or more functional or technical evolutions on an SD environment and also on the MAINFRAME of one or more applications.

- Test non-regression of existing functions.

Responsibilities Held:

Functional and technical homologation consultant on SD and MAINFRAME environments.

Work Performed:

I- Management Phase

1 General Monitoring

▪ Monitoring RedMine (RM) requests.

▪ Monitoring CDS activity issues.

▪ Welcoming and monitoring new consultant(s).

2 Steering Committee Meetings

▪ Updating statistical data.

▪ Designing the presentation.

▪ Scheduling the meeting.

3 Monthly Closing

▪ Updating statistical data.

▪ Designing the presentation.

▪ Scheduling the meeting.

II- Planning of homologation requests to be carried out.

III- Analysis Phase

▪ Reading and analysis of SFG and SFD.

▪ Scheduling meetings with the Business or IT department if more details are needed.

▪ Writing the test strategy and test plan.

▪ Estimating the time for test design and execution using the UO catalog.

▪ Communicating the test execution schedule, start, and end dates.

IV- Design and Execution Phase

▪ Designing test cases.

▪ Executing tests.

▪ Communicating the test progress percentage.

▪ Creating homologation anomalies if needed.

▪ Writing acceptance test reports.

Results Obtained:

Go-live of the evolution(s).

General Context:

The project involves migrating from an old MUSTT solution that is no longer supported (server shutdown) and uses a complex, archaic, and obsolete language, to another TALEND solution. This solution uses an ETL (Extract-Transform-Load) process to perform massive synchronizations of information from one data source (most often a DB2 database) to another SD PostgreSQL database.

The advantages of this TALEND solution are that it is much more modern, simpler, and robust, leading to considerable cost reduction through time savings in Development for maintenance and scalability (e.g., Data Science) or for new functionalities.

Project Subject:

MIGRATION MUSTT-ETL (agile)

Responsibilities Held: QA Consultant

Work Performed:

I- Participation in daily meetings

▪ Daily progress communication via Kanban.

▪ Communication of blocking points and proposed solutions.

▪ Participation in retrospectives after each iteration.

II- Execution of functional and technical test cases

▪ Navigating through different MAINFRAME and SD screens.

▪ Creating, modifying, copying, deleting records.

▪ Comparing pivots before and after evolutions and performing TNR (Non-Regression Tests).

▪ Launching jobs, JCL.

▪ Modifying tables and spytables.

▪ Performing verifications and modifications on different DB2 and PostgreSQL tables.

III- Writing acceptance test reports.

IV- Participation in the continuous integration process (deployment, configuration modification).

Results Obtained:

All flows deployed to production.

Preparation of V2.