Lesson 2 of 6
Roles, skills and career paths
10 min
Listen to this lesson
A TCoE is only as good as the people in it, and SAP testing needs an unusual mix: process knowledge that business people have, test design skill that testers have, and technical skill with SAP Fiori, SAP GUI, IDocs and APIs that developers have. This lesson defines the core roles, shows how to size them, how to assess skills, and how to give people a career so they stay.
Role cards
| Role | Purpose | Key outputs | Contoso |
|---|---|---|---|
| TCoE lead | Runs the capability as a service | Charter, catalog, budget, scorecard, readiness assessments | Priya |
| Test architect (process test lead) | Owns test design for end-to-end processes | Risk-ranked regression pack, release assessments, project test strategies | Two: order to cash and finance; plan to produce and procure to pay |
| Automation lead | Owns the automation portfolio and its health | Automation standards, builds, maintenance, stability metrics | Ravi |
| Test data and environment lead | Makes tests runnable | Data recipes, refresh calendar, masking routine, environment readiness checks | Wei |
| Business test coordinator | Connects the TCoE to a business area | Tester bookings, UAT logistics, evidence quality in the area | Part-time roles in the business; one in Monterrey |
| Key user (business tester) | Judges whether the process works | Executed tests, evidence, defect reports | Twelve named in Detroit and Chicago, plus Monterrey |
| Partner test manager | Runs flexible capacity under the framework agreement | Staffed call-offs, deliverables to TCoE standards | From the AMS partner |
TCoE role cards. Roles are not always full-time jobs; in a small TCoE one person may hold two.
Sizing the core
Size the permanent core from work that never stops, measured in hours, then divide by productive hours per person. Use about 1,600 productive hours a year per full-time person after leave, training and meetings, and check that figure with your own HR data. Contoso's expected year-2 core workload from the business case was about 7,700 hours: release assessments and reviews, TCoE management and reporting, automation maintenance and new builds, data and environment routines, and test design and execution in the regression windows. That is just under five people, which is why the core is five and peaks go to the business network and partner call-off.
A skills matrix for a TCoE
sap-tst-310 introduced the skills matrix for a project team. A TCoE needs a broader one, because it serves many releases and must grow people over years. CTAL-TM v3.0 groups competence into areas such as professional, methodological and social skills, and recommends assessing people with typical tasks rather than self-ratings alone. Contoso rates each person 0 to 4 (none, aware, can do with help, independent, can teach) on these columns:
| Skill area | Examples | Target for test architects | Target for automation engineers |
|---|---|---|---|
| SAP process | Order to cash, record to report, plan to produce | 4 in own process, 2 in neighbors | 2 |
| Test design | Risk-based scope, equivalence classes, end-to-end flows | 4 | 3 |
| SAP technology | Fiori launchpad and apps, SAP GUI, IDoc monitoring, OData | 2 | 4 |
| Automation | Platform skills, maintainability, CI integration | 2 | 4 |
| Test data | Recipes, number ranges, masking | 3 | 3 |
| SAP Cloud ALM | Test Preparation, Test Plans, Test Execution, Defects, Analytics | 4 | 3 |
| Communication | Readiness assessments, facilitation, coaching key users | 4 | 2 |
Contoso's TCoE skills matrix columns with target levels on a 0–4 scale.
Career paths that keep people
SAP testers leave when testing looks like a dead end. A TCoE can offer three paths: a technical path (test analyst to automation engineer to test architect for automation and tooling), a process path (test analyst to process test architect, often a route into a process owner or solution architect role), and a leadership path (test lead to TCoE lead). Key users can follow a fourth, part-time path into the business test coordinator role, which their managers should recognize in objectives.
What would you do?
After the first year, the CIO asks why the TCoE does not simply hire three more people "so we never need partners." Priya's plan shows the core workload is steady at about 7,700 hours, with two peaks a year of roughly 1,000 extra hours each. What is her best answer?
- Core roles: TCoE lead, test architects by process, automation lead, test data and environment lead, business coordinators, key users and partner capacity.
- Size the core from never-ending hours divided by about 1,600 productive hours per person; cover peaks elsewhere.
- Assess skills with typical tasks on a scale such as 0–4 across process, design, technology, automation, data, Cloud ALM and communication.
- Offer technical, process and leadership paths, plus a recognized path for key users.
Check your understanding · not graded
Lesson check
1. How should the permanent core of a TCoE be sized?
2. Which assessment method does CTAL-TM v3.0 favor for skills?
3. Why give an automation engineer one release a year designing tests?
4. Which career path often leads a TCoE member into a process owner or solution architect role?