Kadija Balde

- Requirements definition and analysis

◦ Analysis of existing systems and identification of impacted processes (declarations, tax calculations, regional remittances)

◦ Formalization of fiscal business rules and system interactions

- Writing functional specifications: batch processing and APIs

◦ Gathering & Formalizing needs into detailed functional specifications by use case: Extraction of monthly declarations from oil companies, calculation of local and overseas taxes (VAT, TICPE, etc.), processing of amounts to be remitted by regions

- Setting up testing strategy and execution

◦ Identification of necessary test types: non-regression, performance, and integration tests. Ex: simultaneous processing of multiple declarations for the same period, processing of late or invalid declarations.

◦ Preparation of test data sets using SQL from available databases (Tax Data - Declarations - Remittances)

◦ Execution of automated tests via SQUASH

- Analysis of performed tests

◦ Documentation of results (successes, failures, discrepancies)

- Analysis of technical and functional anomalies and bugs

◦ Collaboration with developers via JIRA to reproduce, diagnose, and correct anomalies

◦ Performing verification tests after correction (non-regression tests)

◦ Writing anomaly reports for tracking and communication with the business unit

Technical Environment:Squash, JIRA, Confluence, SQL, Filezilla, PostgreSQLMethodology:Agile

- Analysis and scoping of client requirements (Build & Run)

◦ Gathering and understanding business needs and requirements (Procurement, Order Management, Shipping, Inventory, Receiving, Packaging)

◦ Identification of impacted business processes and technical constraints (IT flows and logistics flows)

◦ Definition of project budget and timeline

- Formalization of business needs

◦ Writing new business processes in compliance with WMS vendor and SAP ERP specifications

◦ Structuring business processes using BPMN and UML models

◦ Performing non-regression, end-to-end, and acceptance tests

- Functional support for warehouse management software (FR & AN) lifecycle

◦ Configuration and updating of digital equipment versions: RF Scanners and Barcode Printers with technical teams from InfoSys based in India

◦ Monitoring and handling of WMS evolution or improvement requests offshore

◦ Formalization of the different stages of acceptance testing

- Change management and end-user training

◦ Preparing users for software go-live

◦ Writing user guides and operational procedures

◦ Organizing and conducting training sessions for end-users

◦ Implementing new digitized and automated training modules on SAP Enable Now

•Business Analyst Role

-Writing functional specifications and creating mockups

◦ Writing detailed functional specification documents in English.

◦ Designing wireframes/mockups on Balsamiq to illustrate user journeys.

◦ Validating mockups with the Product Owner before development handover.

-Conducting Tests

◦ Designing test scenarios to ensure application stability

◦ Developing and executing non-regression and load tests

◦ Documenting and tracking detected anomalies

-Analyzing IT impacts

◦ Identifying dependencies, risks, and technical constraints (service unavailability, overload, sensitive data leaks)

•Product Owner Role

-Facilitating agile ceremonies (daily, retro, demo, etc.)

◦ Leading and facilitating agile rituals to ensure team efficiency

-Managing project timeline and sprint backlog

◦ Steering the product backlog by prioritizing features based on business value

◦ Organizing work into sprints (2 weeks) and tracking progress with agile tools (E-Vvm and Jira)

-Describing and formalizing requirements with the functional team (Lead support BA)

◦ Gathering and analyzing business needs from stakeholders

◦ Transforming these needs into clear and actionable requirements

◦ Supporting the functional team to avoid ambiguity

-Writing user stories for the development team

◦ Writing user stories with clear acceptance criteria

◦ Using standard formats (As a... I want... so that...)

◦ Continuous interaction with developers for clarification and adjustments

Technical Environment:AWS, JIRA, Balsamiq, E-VVM, Microsoft OfficeMethodology:Agile