Lesson 2 of 5
Team structures
10 min
An SAP test team is never just testers. It is a blend of consultants who know the configuration, business people who know the process, specialists who build automation or data, and coordinators who keep environments and defects flowing. The test lead's job is to design that blend so that every test has someone who can run it, someone who can judge it and someone who can fix what it finds.
The core roles
| Role | Main responsibilities | Contoso example |
|---|---|---|
| Test lead / test manager | Strategy, plan, estimates, entry and exit criteria, reporting, sign-off recommendation | Priya |
| Process test leads | Own test design, execution and quality for one end-to-end process | O2C, P2P, R2R and plan-to-produce leads |
| Test analysts | Write and maintain test cases, prepare data, support execution | Two per process area during SIT |
| Business testers / key users | Execute tests in business roles, judge business correctness, approve UAT | Maria for order to cash |
| Automation engineers | Build and maintain automated regression for stable processes | Small team from cycle 2 onward |
| Test data coordinator | Plans, requests and refreshes data sets; avoids collisions between testers | One for all of client 100 |
| Environment coordinator | Transport schedule, system availability, interface endpoints, refreshes | Shared with the Basis team |
| Defect manager / triage lead | Runs daily triage, chases fixes and retests, reports aging | Rotates among process test leads |
A blended SAP test organization. Small programs combine roles; large ones add layers.
Organize by process, not by module
SAP consultants are usually grouped by module or solution area: sales, materials management, finance. Tests, though, follow business processes that cross those boundaries. A Contoso order-to-cash test touches sales, delivery, inventory, billing and accounting. If test leadership mirrors the module structure, cross-module defects bounce between teams. Give each end-to-end process a process test lead who owns the whole flow and pulls in module consultants as needed.
| Led by module | Led by end-to-end process | |
|---|---|---|
| Who owns a test | Sales, materials management or finance team, each for its piece | One process test lead for the whole flow |
| Cross-module defect | Bounces between teams: "it's a finance problem" | Owned by the process lead, who pulls in the module consultants |
| Contoso order to cash | Five teams for sales, delivery, inventory, billing and accounting | One O2C lead from order for Great Lakes Fleet Services to posted payment |
| Exit judgement | Each module reports green; nobody sees the whole flow | One evidenced view of the end-to-end result |
RACI for the test lifecycle
| Activity | Test lead | Process test lead | SI consultants | Business testers | Process owner |
|---|---|---|---|---|---|
| Test strategy and plan | A | C | C | I | C |
| SIT test design | C | A | R | C | I |
| SIT execution | I | A | R | C | I |
| UAT test design | C | R | C | R | A |
| UAT execution and acceptance | I | C | C | R | A |
| Defect triage | A | R | R | C | C |
| Exit and sign-off recommendation | R | C | C | C | A |
R = responsible, A = accountable, C = consulted, I = informed. Adapt to your contract and governance.
Scaling the team across the program
Team size is not flat. It peaks during integration and acceptance cycles and drops between them. Plan the ramp: analysts join before SIT to write test cases, business testers join for SIT support and lead UAT, automation engineers start once processes stabilize, and a smaller core team carries regression into hypercare and beyond. Booking people late is the most common team-structure failure on SAP programs.
- Before SITAnalysts joinWrite test cases and prepare data recipes
- SITFirst peakConsultants execute; business testers support and judge results
- Stable processesAutomation startsAutomation engineers build regression for processes that stopped changing
- UATSecond peakBusiness testers lead execution; process owners accept
- Hypercare and beyondCore teamA small team carries regression into later releases
Small programs and large programs
Not every program can staff eight distinct roles. On a small roll-out, the test lead may also run triage and coordinate environments, and one process test lead may cover both procure to pay and plan to produce. That is fine as long as each responsibility is still named in the RACI and nobody is judging work they built themselves. On a large program with several waves or company codes, add a layer: a test manager per wave or region under a program test lead, with shared standards, a shared tool and one defect process. The structure scales; the principles do not change.
What would you do?
Contoso's cross-module defects keep bouncing between the sales and finance consultants: billing documents post to the wrong revenue account and each team says it is the other's problem. What structural change helps most?
- Blend configuration experts, business testers, specialists and coordinators by design.
- Organize test leadership by end-to-end process, not by SAP module.
- Use a RACI so every activity has one accountable owner.
- Separate the people who build from the people who judge, and plan the team ramp early.
Check your understanding · not graded
Lesson check
1. Why organize SAP test leadership by end-to-end process?
2. Who should be accountable for UAT acceptance of a process?
3. Which role prevents testers from overwriting each other's data?
4. What is the most common team-structure failure on SAP programs?