The article examines the peculiarities of managing complex IT projects. Their essence is revealed and the classification of factors affecting complexity is presented. In the work, complex IT projects are those that require research and experimental confirmation of project decision-making. It is shown that the complexity can arise already at the beginning of the project, during the formation of its goal, or it can be during the execution of project works, such complexity is related to the complexity of project implementation. The work shows that the project can be classified as complex based on certain qualitative and quantitative factors. The complexity of behavior was considered separately, namely due to the technical complexity of project implementation, which will require the use of complex technologies. This manifests itself as a lack of experience and appropriate skills in the project team. To ensure effective management of complex IT projects, developers use flexible management technologies, Agile, which reduce project uncertainty through iterative development. But when the project team does not have much experience in product development, or does not have the technology, when the result of the application of innovations in management is unknown in advance, research and experimental confirmation are used. To overcome the complexity during the implementation of IT projects, it is recommended to use the approach called Spikes in English. The work presents the author's interpretation of the definition of Spikes and examples of their application. The relationship between innovativeness and complexity of IT projects in the sense of using Spikes is revealed. For the second group of complex IT projects, where the complexity is manifested at the beginning of the project work, the application of the procedure of research and development works is proposed. The article highlights the author's position regarding the purpose and degree of scientific research in IT projects. It is noted that this approach is used exclusively for obtaining an IT product, not a scientific product. The methods of managing scientific and research works in IT projects are analyzed, their place and importance in ensuring the successful completion of complex projects is shown. The hypothesis management workflow is considered as an element of managing complex IT projects.
Read full abstract