ASSESSING THE IMPACT OF TEAM INTERACTION ON THE QUALITY OF SOFTWARE PRODUCTS IN STUDENT IT PROJECTS

Abstract

An effective development of software products in modern conditions is possible only under the condition of well-organized team interaction during the implementation of project tasks. In educational practice, particularly within student IT projects, the quality of software products often differs significantly even when participants have similar levels of theoretical training and technical knowledge. This difference is primarily caused by the specific features of team interaction, including communication practices, task coordination, role distribution, and the use of collaborative engineering tools during the software development process.

This paper presents the results of assessing the impact of team interaction characteristics on the quality of software products developed within student IT projects. Software quality is considered as a combination of functional completeness, reliability, code quality, and maintainability, which are the most relevant indicators for evaluating development results in an educational environment. Particular attention is paid to the influence of organizational and engineering aspects of teamwork, such as joint planning of tasks, coordination of activities, use of version control systems, code review procedures, and team-based testing practices.

The assessment is based on a logical sequence that connects a specific team interaction factor with its manifestation in the development process and the resulting impact on software quality indicators. Such an approach makes it possible to analyze the influence of teamwork on development outcomes without the use of complex experimental measurements. The evaluation can be carried out through the analysis of project artifacts, including source code repositories, change histories, documentation, and testing results, which ensures the practical applicability of the proposed approach in the educational process.

The analysis shows that collaborative engineering practices have the most direct impact on the reliability and quality of software products, while organizational factors create the necessary conditions for their systematic application. The obtained results can be used to improve the objectivity of evaluating student IT projects, to identify the causes of typical development errors, and to justify recommendations for improving the organization of team work in project-based learning.