Domain Storytelling: Users and Developers Model Together
Domain storytelling is collaborative modeling: users tell stories from their domain, the team draws actors, work objects and activities as a diagram.
Podcast: Software Testing, AI and Quality Insights : Page 15 of 16
Coaching Lessons for Testers: Clarify the Assignment First
Software testing starts with clarifying the assignment, or errors surface late and get expensive. One of several lessons testers can take from coaching.
Team Alignment with OKR: Goals That Survive Day-to-Day Work
Team alignment with OKR needs three to five early metrics, health metrics as a counterweight and a neutral facilitator who guides goal setting.
Overcoming Resistance to Change Starts with the Process
Overcoming resistance to change means addressing the transition and the identity people lose. Skeptics become allies, and emotion beats slide decks.
Green IT: Fewer Features, Less Data, No Idle Machines
Green IT makes software draw less power, green by IT uses software for sustainability. How the Pink Index, caching and smaller cloud nodes help.
Software Testing: Pay Based on Performance Rather Than Time
Software testing paid by test cases, coverage and errors found: how Europe's first independent test lab worked in 1978 and which principles still hold.
Liberating Structures: Get Every Voice into the Test Meeting
Liberating Structures like 1-2-4-All, Troika Consulting and TRIZ end meetings where everyone nods at the boss. Testers use them to uncover risks.
Model-Based Testing Without UML: Flowcharts Are Enough
Model-based testing doesn't need UML: boxes, arrows and a flowchart uncover requirement gaps early and generate manual and automated test cases.
Monolith to Microservices: Cut Out Domains Step by Step
Moving from monolith to microservices works by cutting out domains step by step, backed by CI/CD and resilience tests. Greenfield rebuilds rarely last.
Test Intelligence: Finding More Bugs in Less Time
Test intelligence finds 80% of errors in 1% of the runtime with test impact analysis, and test gap analysis shows untested changes before release.
BDD Scenarios: Gherkin Written Afterwards Is Not BDD
BDD scenarios look simple, but Gherkin without real team conversations costs more than it brings. Why five to seven steps keep a scenario readable.
The ISTQB CTFL 4.0 Makes Testing a Team Responsibility
ISTQB CTFL 4.0 unites classic and agile testing in one syllabus and treats test management as a team role. Existing certificates remain valid for good.
Sociable Unit Testing: Testing Use Cases All the Way to the Database
Why do teams write hundreds of unit tests, yet the software still doesn't run? Because isolated tests alone don't prove that a feature works.
Gamification in Software Testing: Gaming Reveals Edge Cases
Gamification makes manual testing fun and keeps risk analyses out of the drawer. Riskstorming, Bingo Bongo and Maturity Poker reveal edge cases.
Systematic Testing: Exit Criteria Indicate When It’s Enough
Systematic testing picks risky and everyday inputs, and exit criteria show when you have tested enough. Complete testing is mathematically impossible.
C++ Core Guidelines: Ownership Is the Most Important Rule
The C++ Core Guidelines by Stroustrup and Sutter put ownership first: does code own a resource or only borrow it? Getting it wrong crashes programs.
User Feedback at MOIA: When Colleagues Are the Users
How MOIA collects user feedback from its own drivers: monthly surveys, mockup interviews, test drives and slow rollouts to 20% of the fleet.
House of Agile Quality: Roles, Approach, and Tools as Pillars
The House of Agile Quality rests on a test foundation and three pillars: roles, approach and tools, topped by lean quality engineering methods.