Programme
- Programme Director
- PMO Lead
- Change and Adoption Lead
- Training Lead
Programme Staffing Blueprint
Oracle Fusion implementation
The team shape and the sequence for an Oracle Fusion implementation, including the two streams that most often delay a pilot.
The phases
Phases, as the method names them.
Named the way the programme names them, so the shape below maps onto the plan you already have.
- Plan
- Design and Configure
- Validate, through conference room pilots
- Deploy
- Operate
The team
Who the programme needs, by stream.
Grouped the way a programme is actually staffed and governed, rather than by seniority or by contract type.
Architecture
- Fusion Solution Architect
- Integration Architect, Integration Cloud
- Security and Roles Architect
- Reporting and Analytics Architect
Functional, ERP and SCM
- General Ledger
- Payables and Receivables
- Fixed Assets and Cash
- Tax
- Procurement
- Projects
- Inventory
- Order Management
- Manufacturing
- Supply Planning
Functional, HCM
- Core HR
- Payroll
- Absence
- Talent
- Recruiting
Functional, EPM
- Planning
- Financial Consolidation
- Account Reconciliation
- Enterprise Data Management
Technical
- Integration Cloud Developer
- Reports Developer, Publisher, OTBI and Data Intelligence
- Data Conversion Specialist, FBDI and HDL
- Visual Builder Extension Developer
- Roles and Security Specialist
Quality and cutover
- Test Lead
- Conference room pilot Coordinator
- Cutover Manager
- Hypercare Lead
Sequence
Who is on in which phase.
The sequence is the part that gets planned last and hurts first.
- Plan
- Solution Architect, Programme Director, PMO
- Design and Configure
- Functional streams at peak, Security and Roles Architect, Integration Architect, Data Conversion Specialist
- Validate, through conference room pilots
- Pilot coordination at peak, Test Lead, functional streams, reporting developers
- Deploy
- Cutover Manager, payroll parallel runs, training, hypercare planning
- Operate
- Hypercare Lead, quarterly update regression cover
Under-scoped
The roles that are always scoped too late.
Each of these is recoverable when it is planned and expensive when it is discovered.
- Security and roles design
- Oracle's role model is the single most common cause of a delayed pilot. Started late, it blocks every downstream test.
- Data conversion
- FBDI and HDL loads are treated as a technical chore. Iterations multiply and the pilot slips.
- Quarterly update regression
- The one nobody staffs for at all. Oracle updates on a fixed cadence after go-live and there is no team left to test it.
- Reporting
- Assumed to come with the product. Users do not accept the system without their reports.
- Payroll parallel runs
- Under-planned, and payroll is the one workstream that cannot be soft-launched.
- EPM data integration
- Planned as a separate project, then found to depend on the same conversion team.
What we screen for
The hardest roles on this shape, and the evidence we ask for.
Ask for the parallel run they got wrong and what they changed.
- Security and Roles Architect
- Data Conversion Specialist
- Payroll lead
Ask
Ask for the planning pack for your programme.
Tell us the shape you are running and we will come back with the staffing plan against it.