Lesson 4 of 6
Knowledge and asset ownership
8 min
Listen to this lesson
A TCoE's value sits in its assets and its knowledge: the risk-ranked regression pack, the automated tests, the data recipes, the runbooks, the evidence of past releases, and the people who know why each test exists. If those live in a partner's tools and heads, the company does not have a TCoE; it rents one. This lesson covers how to keep the assets owned by the customer and the knowledge retained when people and partners change.
The asset map
Rules for ownership
- Customer-owned tools. Test cases, results, evidence and defects live in Contoso's SAP Cloud ALM tenant. The tenant is provisioned for Contoso's own customer number through SAP for Me, and users log on through Contoso's Identity Authentication tenant, so Contoso decides who has access, including partner staff.
- Customer-licensed automation. Automated tests run in a tool licensed to Contoso, with scripts in a Contoso-owned repository. If the partner brings its own framework or accelerators, the contract grants Contoso a perpetual right to use and change them after the partner leaves.
- Intellectual property clause. Deliverables created for Contoso, including scripts, recipes and documentation, belong to Contoso. The partner keeps its general know-how.
- No shadow repositories. Spreadsheets of test steps, local copies of scripts and private wikis are not allowed as the master. If it is not in the system of record, it does not exist for acceptance.
- Identity under customer control. Partner users are named, created and removed by Contoso's administrators, reviewed in Nadia's quarterly access review, and removed on the day a person leaves the service.
| Asset | Home | Contoso owner | Partner role |
|---|---|---|---|
| Test cases, plans, results, defects | SAP Cloud ALM (Contoso tenant) | Priya | Creates and maintains to standards |
| Automated tests and framework | Contoso-licensed tool and repository | Ravi, TCoE automation lead | Builds and repairs |
| Data recipes and golden data catalog | TCoE repository and catalog | Wei, TCoE test data and environment lead | Runs and replenishes |
| Runbooks and handover templates | TCoE knowledge base | Priya | Keeps current within 10 working days |
| KPI workbook and benefits register | TCoE workspace | Priya | Prepares extracts |
Where each asset lives and who owns it. The partner works inside Contoso's homes, never in its own.
Keeping the knowledge
Assets are explicit knowledge, written down. Much of what makes a test team effective is tacit: why a test exists, which data quirks break it, which key user to call about a strange billing result. Tacit knowledge leaves with people. A TCoE retains it on purpose.
- Write the whyEvery critical test case records the risk it covers and the escape or requirement behind it
- Pair the rolesProcess twins onshore and offshore; two people trained for every critical skill
- RotateOffshore staff spend a regression window in Detroit; TCoE staff review offshore work weekly
- Reverse transferThe partner teaches back what it learned, recorded and stored in the knowledge base
- CheckTwice a year, named people demonstrate key tasks without help
Count how many people can do each critical task, the "bus factor." At Contoso, the first count found that only one offshore engineer could repair the automated tests for period-end close, and nobody at Contoso could. Both facts went on the improvement backlog: a second engineer was trained within a month, and Ravi, the TCoE automation lead, learned the repair as part of reviewing the partner's work.
What would you do?
A partner wants to use its proprietary automation accelerator for Contoso's regression. It speeds up scripting, but scripts built on it will not run without it. What should Priya require?
- Map every test asset and give each a Contoso owner and a home in a Contoso-owned tool.
- Keep partner identities under Contoso's control and secure perpetual rights to any partner framework the scripts depend on.
- Retain tacit knowledge with recorded rationale, paired roles, rotation, reverse transfer and periodic demonstrations.
- Measure the bus factor and keep at least one Contoso person able to perform every critical task.
Check your understanding · not graded
Lesson check
1. Why does a Contoso-owned SAP Cloud ALM tenant protect the TCoE's assets?
2. What is a "bus factor" in the context of a TCoE?
3. What should "reverse knowledge transfer" produce?
4. The partner keeps its own spreadsheet of test steps as the master copy because it is faster to edit. What does Contoso's ownership rule say?