What’s Software Quality, after all? — Lu’s Newsletter — Issue #12
We talk a lot about quality, we rarely stop to explain what we mean. Quality is intrinsically connected with agility, so building effective, agile teams comes from being able to build quality incrementally. Knowing how to measure it is an important step in that way. So this issue dedicated to that subject. Share it with others to help build a shared understanding :) originally posted @Revue
What’s Software Quality, after all?
Quality is one of those terms thrown around that people assume we get what it is. Different people see different details of quality and talk as if it was the same thing. That’s a significant part of why engineers fail to get time to work on architecture, product managers fail to understand why things are taking so long, and Quality Analysts fail to assess quality. We all want to build great products but have a different view of what great means. So let’s try to create a shared understanding, but first, let’s see what’s wrong with how each group usually talks about quality.
The Problem with how Product Managers and Designers talk about quality
Product Managers and Designers care a lot about the User Experience., about the User’s Journey making sense, doing what it promises, and being delightful. They care about learning what matters most to the users, and being able to ship features fast is a great way to do that. This is what they’re looking for when they talk about quality. It makes a lot of sense; what’s the Problem with that?
What's Software Quality, after all?
Your users when you forget about quality - Photo by JESHOOTS.COM on Unsplash Quality is one of those terms thrown…
The ISO 25010 Quality Tree Model is my favorite way to describe software quality, but it’s not the only one. In the Fundamentals of Architecture Book the authors also describe the concept of Architecture Characteristics or Ilities. Check them out in these reading notes:
Other people defend simpler, shorter models that are tailored already to what matters most to the business:
At QuintoAndar, we have created our own set of architectural characteristics that we evaluate. At the end of the day, you have to focus on what matters most for your users. The following article presents the idea.
Software Architecture Analysis
🕵️♀️ Collect software architecture data and improve your software quality 🕵️♂️
Thanks for reaching this far 🤗
If you have any feedbacks &/or ideas for the next issues please send it to me and I’ll make sure to read and act on it.
If you liked this content, share it with others who might like it too, and thanks a lot for reading it :)