Quality is not just about testing despite the stereotype. Besides, is it really up to QA to do the tests?
We set about working on this theme during our last round table “Making Quality. Without tests. “. This article summarizes the main points we shared.
Software quality is still too often found only associated with testing. Real challenges of value perception, communication, and collaboration are at the heart of this issue.
I thank the participants for their presence and contribution:
CFOs are accountable for finance, COOs for operations, this is all quite clear.
For Enterprise Architecture, the CEOs is usually the ultimate responsible outside formal Chief Architect roles.
But who’s clearly responsible for your software quality architecture?
“Architecture” is transversally present leading to regular confusion: are we talking about enterprise, functional or technical architecture?
Creating software is supported by a system referred as SDLC — Software Development Life Cycle — that is architectured, intentionally or not.
Software quality architecture is usually diluted through the organizations in different functions, resulting in a poor and inconsistent inclusion.
In fact, where is your…
“It is what it is”, a sentence available in quite all languages.
It took time for me to understand its real meaning and what to do about it, especially in software quality.
In its French version, “il faut faire avec”, I was interpreting it like something to accept anyway, passively, and usually not accepting it.
When I went to Portugal, I heard “É assim”, linking it back to hard times that had to be endured.
When I started to change my perspective to confront ourselves to reality, as it is, to react better, I gave all its value.
Quality Assurance is probably the most common definition for the QA acronym. The pressure of the ecosystem towards Quality at Speed requires additional meanings for QA.
Acronyms are useful to build a shared meaning of a particular concept. At the same time they shorten exchanges, they also tend to close their understanding to a particular domain. QA can be tied to specific roles or activities, such as Quality Analyst or Quality Assessment, but the most valuable acronyms have to bring an increasing value regarding the existing practices.
The evolving role of Quality Assurance is identified as a key trend part…
The last deployment on Friday went well: no service interruptions or incidents. All technical monitoring is green. However, on Monday morning, customer complaints were raised.
Our Definition of Done does not include Functional monitoring. The team culture did not yet have this reflex in its interactions, where a checklist would have been helpful.
A systematic structure can help us improve the quality of our software building processes. A technique resulting from the consulting practice is available: MECE.
This article shares the definition, value, and how to use MECE in the context of Quality Engineering. …
Our level of understanding and ability to predict systems aims to be increased by technologies; it is still necessary to have the structure of reflection allowing us to navigate there.
Accelerating decentralized decision-making bringing overall value is a constant quest for organizations. Staying competitive is a priority in an increasingly uncertain, complex, and interdependent ecosystem.
This article shares the different models helpful in analyzing the context to adapt our actions. The applicability of each paradigm is identified before concluding on the implementation of a Quality Engineering initiative.
Let’s start with VUCA, an acronym so popular with consultants.
This acronym appeared…
Anass El Bekali shares his perspective of a transverse IS quality at the customer’s service in this QE Unit interview.
With more than 20 years of experience in various sectors, complex organizations, and various missions, Anass shares his practices and concrete anecdotes.
It provides us with structuring points on continuous improvement, the cost of non-quality, and arguments to use with decision-makers.
This sharing leads us to reflect about a quality at the heart of IS, collaborative, iterative, sustainable, and at the service of customer satisfaction.
Join the QE Unit to access exclusive and regular content from the community.
The delivery of the last release took weeks of delay, only to realize that the features are not suitable for customers. Despite sprints and colorful graphics, the quality is not there. The board decides to act.
We are asking you for a concrete and actionable investment plan to reverse the trend starting next week. The need to use modern solutions is clearly stated. You have to “capture value” and “quickly”.
Hitting a wall is one of the triggers for investing in software quality. Businesses often want quick, short-term results. …
How many times have you participated in a meeting where the problem is not identified, stated, or written? Personally, too much.
I remember as a child hearing my godfather saying “at work, we are paid to solve problems”. It sounded a bit negative at first, but I got it better with time, and with experience, feel what he meant. We can summarize the work of engineering in solving technical problems but the reality is, we must be solving customer problems.
McKinsey is one of the most famous consulting firms over the world, owning a tremendous reputation of high quality and…
We explore the repository models ecosystem in our previous series of articles. We look at its definition, myths, and practices in other actors. It is still not enough to select a repo model.
We can jump too quickly to solutions that are hazardous without being clear on the problem to solve. A problem that is not solely technical and starts with the business.
This article aims to guide your repository model decision using a holistic quality engineering perspective and process.
It is worth investing time in the first place to clarify the “Why” of your initiative. Why are you considering…
The Quality Engineering Unit is a community dedicated to improving our software quality practices through transversality.