Continuous Everything - Do we need it?
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.
Conversations with testers, developers, and coaches who work in the field.
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 is a thing of the past. Domain storytelling turns users and developers into a joint team before the first code is created.
What does coaching have in common with software testing? More than you might think: clarifying orders, recognizing patterns and dealing with errors as real quality 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 doesn't fail because of the idea, but because of the process. Why skeptics are valuable allies and how emotional connection moves more than any presentation.
Sustainability in software development has seven dimensions, but most people only know one. What carbon footprint, frequency of use and green features really 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 in which everyone nods and nobody really thinks? Liberating Structures solves exactly that, with concrete formats for teams that want to test better together.
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 it is largely a question of organization. Why monoliths, DBAs and silos often slow things down more than the infrastructure.
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, risk analyses end up in a drawer. Gamification in testing can solve both - with concrete formats such as Bingo-Bongo or Maturity Poker.
70.000 copies sold, but testing is still considered destructive. Why this image is wrong and what it really means to test software.
C++ is 45 years old and yet deeply rooted in autonomous driving, medical devices and AI libraries. What the Core Guidelines have to do with it.
How do you test an app that drivers use while driving without distracting them? Test drives, surveys and slow rollouts on 20% of the fleet.