
Evolutionary quality
Demanding maintainability early while the market is still missing is wrongly prioritized. The evolution model shows which quality goals count.

Demanding maintainability early while the market is still missing is wrongly prioritized. The evolution model shows which quality goals count.

In automotive testing a windshield wiper already counts as a safety-critical system. What that means for test methods and for standards.

Out of 73 universities audited, they had to abandon one in five because there were too many gaps. What this means for software security.

Shift left sounds good, but does it really make a difference? How six years of data show what Continuous Everything actually changes and what it doesn't.

Throwing specifications over the fence belongs to the past in modern software projects. Domain storytelling unites users and developers.

Coaching and software testing share far more than most people expect in daily work. Clarifying orders and spotting patterns are real levers.

Good team goals don't fail because of the concept, but because they disappear in everyday life. Three to five metrics and a moderator change that.

Change does not fail because of the idea, it fails because of the process around it. Why skeptics are allies and emotion beats slide decks.

Sustainability in software development has seven dimensions and most know only one. What carbon footprint, use and green features mean.

outsourced in 1978, paid according to test cases and errors found: Why this approach failed back then and which principles still apply today.

Meetings where everyone nods and nobody really thinks can be designed differently. Liberating Structures provides the concrete formats.

Model-based testing is considered complex and formal. Boxes, arrows and a flowchart are enough to uncover requirement gaps early on and generate test cases.

Cloud migration sounds like technology but is largely a question of organization instead. Monoliths, DBAs and silos slow things down most.

Finding 80% of errors in 1% of the time: How test impact analysis and test gap analysis are fundamentally changing testing.

BDD looks simple, but it's not. Why Gherkin without real team communication creates more effort than benefit, and how to do it right.

Two years of work, an international team, a completely revised basis: what has really changed in ISTQB Foundation Level 4.0.

Why are hundreds of unit testers created, but the software still doesn't run? Because isolated tests alone do not prove a feature - and that is the problem.

Manual testing is no fun, and risk analyses usually end up unread in a drawer somewhere. Gamification solves both with concrete formats.