How SAP Public Cloud Changes the Staffing Conversation
By Jeff Sharpe, Co-Founder, Fokis Services
Originally published · Updated
Choosing SAP Public Cloud changes the questions in a hiring brief. It does not automatically remove the need for consultants, nor determine a project’s duration or cost.
The useful question is: what work must your team deliver, and which capabilities do you already have?
Clarify the extension and integration work
SAP’s Public Edition documentation describes supported extensibility approaches, including side-by-side extensions on SAP BTP. That makes the chosen extension model and integration requirements important topics for technical hiring. Read SAP’s extensibility documentation.
Discuss the actual business requirements with your architecture lead. Then identify the development, integration, testing, and support responsibilities that belong in each role.
Look beyond development roles
A staffing plan should also cover the people who understand business processes and the data moving between systems.
- Functional expertise: Map process responsibilities and decisions.
- Data migration: Assign ownership for preparation, validation, and reconciliation.
- Testing: Identify who will coordinate business scenarios and resolve issues.
- Change and training: Make adoption and knowledge transfer part of the plan.
Choose the engagement for the responsibility
A time-bound migration or testing assignment may suit a contract specialist. Ongoing application ownership may suit a permanent employee. Program leadership needs its own mandate and decision authority.
Public and private cloud environments should not be treated as a simple split between small and large companies. Build the role brief around the selected environment and your organization’s requirements.
Fokis Services recruits SAP and ERP talent for contract delivery, permanent teams, and leadership roles.
← Back to all articles