Speaking of quality, they usually mean some kind of compliance with the requirements. Often, the requirements mean those that are clearly put forward by the customer, analyst or someone else who sets the tasks . It is worse if they are treated as uncontested, and this implicitly leads to an end in itself - to satisfy the customer's requirements. This often happens in outsourcing, and this focus of attention negatively affects the end result - what users see and work with.
We at SmartHead are also engaged in custom development, and I suggest looking at quality more broadly. This is not only about compliance with explicitly voiced requirements, but also about the requirements themselves. About the addition of explicit requirements with our own, focused not on the needs of the customer, but on the convenience of the end user. User experience, usability, texts in the interface, responsiveness, speed of releases, their compliance with expectations - all this also refers to quality.
Quality is about “making it cool” from the point of view of many parties: development, customer and end user.
How to do it? Hard. It is worth starting with the formation of a mindset for "built-in" quality. I will tell you about the principles that can help in this.
Quality is about development, not testing
Why is quality tightly associated with testing? Unclear.
, , , .
, , , . , . «», . — , . , . , , , .
, . «».
, , (, ) , . .
, . - , , . , .
- , « , » .
— , . , , . , , .
—
, , , . , .
( ) common sense, , . . ( ).
— , — , ( Getting Real Basecamp).
— , , ( FFF). , .
, , . — .
,
, . , , , .
— , : , , «»; , , .
, - .
. , , , . . . .
. , . , , , . . - , . . , , .
. , , , . . — .
- . , , . , , , — . .
. .
?
— , , . , . , , . , .
— , , . , : , .
. , , — .
, . , , , .
, , .
— . «» .
.
. , , , .
Testing is a bonus to improve the system, not a critical need.
In the next article, we'll talk about what technological approaches can help you develop well.