Request management
- Validate incoming requests jointly with Operational Process Owner (from stakeholders via GDP) against existing functionality and the pipeline. Advise how current functions can meet the needs or define a new development.
- Categorize (compliance, operational efficiency, product strategy, visibility) and score each request, with the benefit and baseline.
- Refine and write acceptance criteria and test cases, and raise the ITBR with date, score and benefit for
- New developments define the exact requirements, how they interact with the system, and what they affect.
- Change requests, define what changes in existing functionality, and the impact on the process.
Backlog and roadmap
- Rank the modality backlog using the scoring model and fit the Air/ Ocean Product Strategy Manager’s plans into the roadmap.
Alignment and shared core
- Align with the other owners such as ADM and MDM & Quotation owners on common functionality (financial processes, documents, attachments, references). Attend the monthly design forum.
- Coordinate data needs with Data Governance.
- Own the business side of integrations (requirements, data sets, partner expectations, priority).
- Internal development team and integration owner handle the technical side.
Testing and release
- Provide test cases to the Operations Excellence Team (OET), support UAT, review defects, and confirm fixes.
- Maintain the modality’s critical-flow regression pack with the Performance & Insights Analyst.
- Contribute to release readiness and release notes.
Ownership
- End-to-end system process for the modality including any integrations with other applications from system process and data required. Including but not limited to:
- Operational visibility (schedules, status updates, etc.)
- Carrier integrations (CHAMP, CargoSmart, INTTRA, direct carrier integration, etc.)
- Changes required in system when there are regulatory changes, close alignment with Operational Process owner
Stakeholder Management
- Air/ Ocean Product Strategy Manager, joint alignment with PCO for prioritization, development and change request
- Operational Process Owner for operational process and compliance to regulations
- Data Governance for data that will be required in development and change request
- Systems Delivery & Release for development & resource planning, prioritization and communication with vendor
- Operational Excellence Team (OET) for demands and change requests
Decides: Requirement content, backlog ranking within the modality, whether an existing function meets a need.
Recommends: Sprint scope to the Delivery & Release team.
Escalates: Cross-modality and shared-core disputes, vendor sizing disputes.
- 4-7 years in operations or TMS-related systems work
- Strong requirements writing and test design
- Structured system thinking
- Strong industry knowledge
- Strong written and verbal communication skills in English.
