This RACI reflects the future state draft from the Design Thinking session. Rule of thumb: 1 Accountable, 1–3 Responsible, 1–3 Consulted, Informed only when necessary.
Design, Testing, and Deployment are split into two sub-streams where applicable: Non-Technical (ShipperX-led) and Technical (ShipTech-led).
Legend
- A — Accountable (single owner)
- R — Responsible (does the work)
- C — Consulted
- I — Informed
Role Glossary
| Code | Role |
|---|---|
| Dir-X | Director, Shipping Channels (ShipperX) — Cristina Marculescu |
| Dir-T | Director, ShipTech — Dariusz Grabka |
| PDM | Product Manager (ShipperX PMs: George, Kirk, Chris, Iain, Bruno, Saurabh) |
| PM | Project or Program Manager |
| BA | Business Analyst or Product SME |
| DM | Development Manager |
| DL | Dev Lead / Sr. Dev |
| QM | QA Manager |
| UX | UX Designer |
RACI by Lifecycle Stage
| Lifecycle Stage | Dir-X | Dir-T | PDM | PM | BA | DM | DL | QM | UX |
|---|---|---|---|---|---|---|---|---|---|
| Enterprise Prioritization | A | C | R | I | – | – | – | – | – |
| Product Plan & Roadmap | A | – | R | C | I | C | I | I | – |
| Business Requirements / IT Assessment | A | – | R | – | R | – | I | I | – |
| Prioritization | A | – | R | – | I | C | I | I | – |
| Work Plan | I | A | C | I | I | R | I | I | – |
| Design — Non-Technical (stories, UI/UX) | I | – | A | I | R | – | C | – | R |
| Design — Technical (ShipTech-led) | I | C | C | – | I | A | R | – | – |
| Development | I | C | I | – | C | A | R | C | – |
| Testing — Non-Technical / UAT | I | – | A | I | – | – | – | C | – |
| Testing — Technical (unit, functional) | I | C | I | – | C | A | R | R | – |
| Deployment — Non-Technical | C | – | A | I | – | – | – | – | – |
| Deployment — Technical (release execution) | I | I | C | – | – | A | R | – | – |
| Hypercare | I | A | C | – | C | R | – | – | – |
| Operate + Support | I | A | C | – | C | R | – | – | – |
Notes: A remains a single owner for each stage. R and C should stay intentionally small to keep delivery flow efficient.