Project Management Officer
We are looking for a hands‑on Project Manager to help drive a multi-year programme that integrates our core finance systems with strategic third‑party applications.
The program connects the Order‑to‑Cash landscape — collections and cash application in particular — to the enterprise ERPs through a cloud Global Data Platform.
It is delivered wave by wave, and is deliberately designed to be reused across several ERP platforms — SAP S/4HANA, SAP ECC and Microsoft Dynamics 365 — and across multiple countries and regions.
The successful candidate will sit at the center of business process owners, internal IT and architecture, system‑integrator partners, the data‑platform team and the external application vendor, and will keep all of them moving in the same direction.
Responsibilities
Delivery governance
- Own the end‑to‑end plan, scope, schedule, and RAID log for the workstream and each rollout.
- Run the governance rhythm — steering and working sessions, tracking and status reporting to sponsors.
- Manage dependencies, risks and issues proactively.
- Coordinate the test cycles, data‑migration checkpoints.
Solution definition follow‑up
- Contribute actively to functional and technical definitions.
- Facilitate specification workshops with business, IT, architecture, the integration/data‑platform team and the vendor, turning into agreed definitions.
- Maintain traceability between business requirements, interface specifications, data models and test cases.
- Keep the definition backlog moving.
Stakeholder vendor management
- Act as the single point of coordination across business process owners, internal IT and architecture, system‑integrator partners, the data‑platform team and the external application vendor.
- Manage the delivery with partners and vendors.
- Communicate clearly.
Multi‑ERP rollout core‑model reuse
- Plan and deliver successive rollouts across different ERP platforms (SAP S/4HANA, SAP ECC, Microsoft Dynamics 365) and regions, protecting and reusing a common core model and canonical design.
- Ensure region‑and‑ERP‑specific requirements are captured explicitly, without fragmenting the template.
- Capture lessons learned and improve the delivery approach release over release.
#J-18808-Ljbffr