Patient agility: Is agile working dying?
Agility is ailing in many companies, but it is not dead. Two rescue service schemes show where the pain is and what can help now.

Conversations with testers, developers, and coaches who work in the field.
Agility is ailing in many companies, but it is not dead. Two rescue service schemes show where the pain is and what can help now.
Security requirements remain abstract as long as it is clear what the system is supposed to protect. CIA goals, asset analysis and threat modeling as a card game make it tangible.
If you have bad principles and use AI, you will get worse faster. Why agentic engineering needs more than code generation.
The Blue Angel for software really exists - and provides measurable values for energy consumption, hardware service life and user autonomy. The costs and benefits of the process.
AI systems can be tricked into revealing protected data through clever prompts. Where the points of attack lie and what OWASP recommends.
Why can't LLMs do cause-and-effect? And what does Quality Function Deployment have to do with it? The answer changes how you prioritize testing.
Standards do not make secure software by themselves - but 62443-4-1 shows how security really belongs in the process from the very first design step.
From developer to test automation engineer: Why clean code principles decide which automation lasts for years and which doesn't.
How does a product test work before the magazine is published? Independent purchasing, blind testing, multiple verifications - including parallels to software testing.
130 participants, a clear focus on test automation and real practical reports: Why TACON in Leipzig attracts more and more people every year.
60 to 80 participants, no fixed program schedule and yet the most intensive technical discussions of the year: how a barcamp achieves what traditional conferences often cannot.
Test reporting in 5 steps: Goal, position, forecast, data quality and automation. How reporting becomes a real management tool.
Formal methods sound like an ivory tower, but they provide what testing alone can never do: mathematical proof of correct behavior.
527 submissions, just under 50 slots: How a conference program is really created and what makes one submission stand out from the rest.
AI-generated test cases in the medical technology environment: how a RAG system remains regulatory clean without tool validation.
600 production runs, one workflow, not a single test for it: How process mining shows what regression testing really needs to cover.
AI-generated code sounds tempting, but who pays the bill? Why software engineering needs more quality control, not less.
Quality in start-ups is not created by processes, but by attitude. Why testers need to be louder than developers.