Building Рrocesses that Ensure the Development and Release of Software Products

The topic of the master's thesis is relevant, since process management in the field of software development is today one of the key factors ensuring effective development, a high level of quality, optimal use of resources and a decent level of competitiveness. The object of the study is the processes that ensure the development and release of software products. The subject of the study is the effectiveness of requirements, risk and quality management processes for the development and release of software products in the selected company, as well as the general state of the process management system for software products. The purpose of the study is to analyze the current level of process management and its weaknesses in the field of requirements, risks, and quality management in one of the large Russian IT companies. Based on the analysis, it is necessary to propose processes for the development and release of software products, evaluate the results of their implementation and make recommendations for further improvement of the processes. Completed tasks: • An analysis of best product management practices in three areas of process management was carried out; • Interviews with managers, team surveys, group discussions with project managers were conducted and areas of process management that were relevant to departments were identified; • Proposed and implemented processes in selected areas; • The effectiveness of the implemented processes was assessed; • Recommendations for process improvement were formulated. The hypothesis was proven that the creation of a system of software product management processes increases product quality and predictability of development. Research methods: • Analysis of literature on the topic of process management of software development; • Analysis of the most famous and effective methodologies; • Analysis and comparison of current departmental processes; • Conducting a survey of 8 project managers, 5 department heads; • Conducting interviews with 1 senior executive. Requirements management process. Results: • Building a process based on a requirements matrix made working with requirements more structured and clear. • Statistics were collected and an initial assessment was made of departmental performance in processing claims. • When developing a process management tool, it is worth comparing the time that will be spent supporting the process in a specific tool with the time that will be spent on the actual work within the framework of the client request. Risk management process. Results: • The process made it possible not to skip the analysis of potential problems when planning work and to proactively determine a work plan to maintain product quality. • It is worth recording the regularity of risk analyzes in the project to constantly monitor the occurrence of problems and timely draw up a plan to address them. • The risk management process can be continued with the process of introducing changes to the product. It will allow you to take a more conscious approach to changing the product and assess the impact of changes on its quality. Quality management process. Results and recommendations: • Transparency of planning and predictability of delivery dates have increased thanks to the introduction of stages and milestones, with the help of which readiness for release was monitored. • It was possible to establish a minimum quality level for all departmental products and standardize the process of their evaluation by creating a template for release quality criteria and a test plan. • Creation of a checklist and templates for describing bugs optimized the work of the release manager and simplified communication within the team and with the customer. • A common understanding of the severity of bugs within departments made it possible to give clear assessments of problems and collect general statistics on products.