The talk is devoted to exploring the role of each project member in the quality assurance of the project.
Using illustrative examples, we consider that only joint and conscious efforts of all members can guarantee a high level of quality, while a gap in at least one of the steps - planning, analysis, development, test organisation, staff motivation and effective communication within the team - is sufficient to lose confidence in quality.
Any testing efforts can be nullified if you do not apply best practices in programming methods and code organisation. Product quality assurance is possible only if there are requirements that meet the conditions of completeness, consistency, and testability conditions.
Conclusion: it is necessary to strive for the fourth level of maturity of the testing process, where it is not so much the evaluation of the finished product that is important, but rather an integrated approach to quality management of the development process at all levels.