DE — heise online
The Data Governance Drama Before Test Launch and How to Resolve It
Software1 min read
This is a preview of a heise+ paid article about a common problem: test data often has no clear owner, so it goes missing just before a software test starts. The article offers a three-level way to fix this.
What happened
Before a new data system is tested, teams often run short of test data. There are too few records to create realistic workloads, and the existing data does not cover the real business cases. IT points to the business team, the business team points to IT or to the architect, and the project manager waits. Status reports keep saying "test data being clarified" with no real progress.
Why test data gets lost
Teams plan the data architecture with care. They model production data, split it into business areas, and assign owners. But almost no one plans for test data. Because test data belongs to nobody, it is a blind spot. The article says these problems usually come from unclear responsibility, not from poor communication.
Why it matters
If test data is not ready, tests are delayed or run on data that does not reflect real use. Problems may then show up only after the system goes live. A clear rule for who owns test data, set up early in the design, can prevent these delays.
What to watch
- Whether the project assigns a clear owner for test data early in the design
- Whether the three-level responsibility model is used in practice
- Whether the status line "test data being clarified" is replaced with real decisions and deadlines