Jérémy Sarazin

I was in charge of 4 different projects, all in production and used daily by SNCF TER agents. The biggest challenge was to define, plan, and successfully carry out the opening to competition, which impacted three of the four projects and had an unchangeable opening date.

Achievements:

EasyTER is the main application for SNCF TER customer relations agents. The application depends on numerous services within SNCF's IT department. I was responsible for managing the numerous evolution requests, coming from the TER business or from services related to EasyTER, monitoring development and deployment, carrying out testing, and communicating with requesters and other affected services.

Service à bord concerns only two regions in France. It is a mobile application with few features, and I only needed to manage technical and corrective maintenance.

EasyDoc has both a customer interface and an administration interface. Most of the evolution requests concerned the administration, which is also the most complex part because the functionalities and the administration interface depend on the connected user's profile. Furthermore, any evolution of this interface can impact the customer interface.

RapporTER is a PowerApp with three parts: an Agent interface, a Manager/Expert interface, and a Power BI section available for Managers and Experts. During my assignment, I had to manage corrective and evolutionary requests on all these interfaces.

These four products are developed by three different companies, external to SNCF. There are also two different teams within another company to manage user support. Therefore, good organization was necessary to properly follow all subjects and provide the necessary visibility to the right stakeholders.

Project: "Logbook" then redesign of the main mobile application. The "Logbook" project is an in-app feature within the PulseLife application. The goal is to target medical interns in France and then in other countries so they can have a space to record interventions and procedures performed during their internship.

I then moved on to one of the company's major projects: the complete redesign of the mobile application. It was necessary to start from scratch as there was a desire to change technology, improve the application's UX/UI, remove certain features, and add new ones.

Achievements:

As the "Logbook" project started "from scratch," I was able to define, in agreement with the other team members, how we wanted to work (tools, rituals, method). I was then responsible for gathering requesters' needs, framing them, prioritizing them, and writing User Stories accordingly. I had to report to the various stakeholders and test the developments as they were delivered. I was also tasked with co-creating and challenging the mockups and functionalities associated with customer needs.

Regarding the mobile application redesign project, I joined the project towards the end of the scoping phase. I was able to co-build the roadmap, functionalities, and user interfaces. I then wrote the associated user stories. We were able to start development, which I followed and tested for about 4 months before having to change assignments due to major strategic and organizational changes within the company. The project was well underway but far from complete, as approximately 1 year of development was still planned.

Project: Services Portal then Cortex

The first project I started my assignment with was a services portal. A POC had already taken place, and the idea was to take it over to frame the need and industrialize it.

Less than 2 months after my arrival, I was asked to move to a strategic project for the company: Cortex. This is a foundation comprising several technical components and administration screens, allowing different software (internal and external) to use data, certain screens, and certain functionalities to centralize information and avoid redoing developments, which are thus shared within Cortex.

Achievements:

On the services portal, my work was that of a "classic" PO: creating user stories, prioritizing the backlog, interacting with developers and UX/UI designers to clarify needs and make functional choices...

On Cortex, my work was much closer to a project manager because the development was outsourced to a service company, the project had started about a year ago, and there was already a project director to set priorities and direction. Therefore, I mainly performed monitoring tasks, coordination meetings, testing during deliveries to validate certain functionalities, and creating mockups to provide developers with a basis for work/reflection for the future.