Programme
- Programme Director
- Delivery Lead
- PMO Lead
- Change and Adoption Lead
Programme Staffing Blueprint
Salesforce multi-cloud programme
The team shape and the sequence for a Salesforce multi-cloud programme, including the skills most often assumed to be interchangeable.
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.
- Discover
- Define
- Design
- Build and iterate
- Deploy
- Optimise
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
- Solution Architect
- Technical Architect
- Integration Architect, MuleSoft
- Data Architect
- Identity and Access Architect
Cloud and functional
- Sales Cloud
- Service Cloud
- Marketing Cloud, including Journey Builder
- Experience Cloud
- Data Cloud
- Revenue and CPQ
- Field Service
- Agentforce
Technical
- Apex and Lightning Web Components Developer
- Declarative and Flow Specialist
- DevOps and Release Engineer
- Data Migration Specialist
- QA Automation Engineer
Quality and cutover
- Test Lead
- User Acceptance Coordinator
- Release Manager
- Hypercare Lead
Sequence
Who is on in which phase.
The sequence is the part that gets planned last and hurts first.
- Discover
- Solution Architect, Programme Director
- Define
- Adds functional cloud leads, Data Architect, Change Lead
- Design
- Technical Architect, Integration Architect, Identity Architect, DevOps Engineer stood up early
- Build and iterate
- Developers and declarative specialists at peak, QA Automation, Data Migration
- Deploy
- Release Manager, Test Lead at peak, training, hypercare planning
- Optimise
- Hypercare Lead, adoption measurement, retained release 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.
- Release engineering and DevOps
- Stood up late, so metadata deployments are manual and every release becomes an event.
- Data migration and de-duplication
- Underestimated because the object model looks simple. Duplicate records destroy user trust in week one.
- Marketing Cloud specialists
- Assumed to be interchangeable with core platform people. They are a separate skill and a separate market.
- Identity, permissions and licence design
- Discovered at user acceptance testing, when the licence mix turns out to be wrong.
- Adoption and enablement
- The clouds go live and the pipeline data stays incomplete, so the business sees no value.
- Data Cloud and Agentforce skills
- New, scarce, and now assumed to be part of a standard build team.
What we screen for
The hardest roles on this shape, and the evidence we ask for.
Evidence of a live release train, not a sandbox.
- DevOps and Release Engineer
- Data Migration Specialist
- Marketing Cloud 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.