The delivered software must provide business value, else it is likely to be another useless or side-project.
Like in finance, software delivered now has more value than later. Thus increments and improvements are key differentiators.
A transversal end-to-end perspective enables to improve a system, in contrary to local optimizations usually generating negative side-effects.
Various techniques and skills must be combined to deliver quality software, we must combine Design Thinking, Architecture among others.
Quality is a team responsibility. Quality Assurance is not only Testing, not only Manual Testing, and not restricted to one silo.
A transversal collaboration from Product Management, Architecture, Dev, QA, Security, and Ops will bring significant value to the organization.
Antoine & The Quality Engineering Unit
Hi there, I’m Antoine Craske, the founder of the Quality Engineering Unit.
Delivering software is a complex activity. I have personally been involved in challenging ones over the last 10 years.
Across those experiences, I have see repeated patterns of lack of transversality between functions leading to inefficient systems.
Even if we gracefully accept DevOps as a de-facto standard nowadays, I feel that we still approach Software Quality in silos.
This is why I decided to create this community for a transversal perspective on software quality.
I decided to name it Quality Engineering Unit to represent this community of practice.
I aim to provide relevant, useful and regular content, adapting them based on the experience and feedbacks.
If you have any suggestion or comment, feel free to share by reaching me on the contact page.
I would be happy if you decide to join the newsletter where I share weekly updates far from social media.