In the fast-paced world of digital imperative, software quality is not just about finding and fixing defects. It’s about building a software production system that thrives on quality and speed as a business enabler. The recent work enables to introduce the Quality Engineering Starter Kit — a comprehensive resource designed…

Definitions set the frame. From the Old French “definer”, definitions structure concepts by clarifying its boundaries, elements, and interactions — three elements we will cover in this article dedicated to Quality Engineering in the software industry. The Quality Engineering definition you will find in this article builds upon the evolution…

Software production is hard. To succeed in this dynamic environment, organizations need a comprehensive and cohesive approach that consolidates the big picture while enabling focused and effective action. This is where MAMOS, the Quality Engineering Framework, enters into play. MAMOS acts as a guiding compass for organizations to map their…

Another day, another initiative. People enjoy launching new things — it contributes to a sense of novelty, progress, and social validation. The main problem is when we want to build something on top of unstable foundations. And that’s what happens too often in software: 95% of organizations launch digital and…

Waiting-time is hard to get rid of. I believe there’s no need to argue on its business impacts between the cost of delay, team frustration, idle costs, plus late rework — the point is how to get rid of it. Waiting-time is complex due to its multi-causality within the software…

Accelerate solving your Quality at Speed pains. We all need more speed. But we have a complex problem to solve: Trade-off quality makes us slower Quality practices initially slow us down Methods or technology alone are not enough. My experience from software engineer to CIO/CTO convinced me that we can…

Microservices? No. Technology-driven approaches often prioritize the latest trends over practicality and business needs, leading to complex and unnecessary architectures. Microservices, for example, have become a buzzword that many adopt without fully understanding their implications. Businesses need efficient software architecture that maximizes current and future flexibility to remain competitive in…

Principles shape us. And when under pressure, our survival mechanism will make us rely on the underlying consequences of our principles. That behavior is good in itself — but issues arise when invalid principles make us take the wrong decision, even more under the constraint of time. And in today’s…

$2b annual revenue. That’s the scale at which companies studied had good reasons for Microservices architecture. And before that? A Monolith architecture evolving to a Modular Monolith, Service-based, and only then to Macroservices, Miniservices, Microservices make the job. Why is that? The solution with minimal efforts must be the preferred…