Context. Software Development has been witnessing great innovations over past few years with good number of technologies, tools and practices invading the industry. Client demands and collaboration in the development process are also seen increasing. So many new practices and methodologies are coming up and Agile is one of prominent practices adopted by many. Even in Agile, Scrum methodology is picking up more demand presently. As Software Development process and practices are changing so are the leadership styles in the same. Leadership is critical for success of any team. This study intended to explore this model and requirement of leadership in Scrum based Software Development in a practical scenario. Objectives. Leadership, which is essential in any Software project, differs from Traditional Methodology to Scrum Methodology of Agile practices in Software Development. Through a case study, the author attempted to investigate and explore the perspective of Leadership requirement in Scrum based Software Development in a practical scenario. The study aimed to gather and analyze the Leadership model implemented in two domestic projects in an Indian company, involved in two distinctive domains, and sum up the impressions gained in the same. The study aimed to assess whether the gathered knowledge adds up to the existing body of knowledge on the phenomenon or on the contrary whether any suggestions for improvement can be given to the case units. Methods. Case Study method was chosen for undertaking this explorative study. A literature review was conducted prior to the case study to gain knowledge on the phenomenon, which also answered one of the Research Questions and helped partially the other. A multiple case study was conducted through semi structured personal interviews, tools analysis and direct observation in the case units. Qualitative data analysis was made using Grounded Theory on this three orders of collected data. The results were compared with the Literature and conformity or variance analyzed. This comparative analysis is used for making recommendations to the case units for improvement or for additions to the existing body of knowledge. Results. Through the results of Literature Review, Leadership models in Software Development including Agile Scrum were summed up. And through the results of the case study, the leadership models and features implemented in the case units have been identified. These results are further validated and contrasted with the results of the literature review. How the literature models and the case unit models of leadership differed is studied. The justification for the implemented leadership model in the practical situation is also analyzed. Following, a review of the models employed at the case environments, the perspective of leadership in the two Scrum based Software Development projects is summed up. At the end, it is assessed what effect the case study would have on the existing body of knowledge on the phenomenon and modifications that can be proposed to the case units based on the results and analysis. Conclusion. It is concluded that the Case Units are implementing Situational Leadership and Transformational Leadership in a mixed way. Telling and Selling models in Situational Leadership are prominent while Participating and Delegating are ranking less. Some of the important features of Transformational Leadership like Self Management, Organizational Consciousness, Adaptability and Proactive are in implementation but not all features of the model are assumed. Even Scrum is implemented in a modified way, extending only controlled autonomy with higher monitoring and it had a direct effect on the leadership. On the whole it is directive leadership that is in play with co-existence of collaborative one situationally.

Agile methodology has existed for over a decade – its potential benefits have made it attractive and popular. As part of innovation, public organisations increasingly invest in information technology systems. Nevertheless, complex information technology adaptive systems require adaptability and flexibility to improve public organisations' delivery systems. Even though the Agile methodology can increase productivity and quality, adopting agile scrum methodology in public organisations is challenging. This study investigates public organisations where IT projects have unclear requirements and cross-functional team environments – which the scrum methodology is typically best suited for. However, despite the widely spread agile method concept and the need increased in the last two decades, still public organisations are not fully adapted to agile scrum methodology, and researchers have noticed slow and ineffective changes in adopting it. While many studies are available on challenges in adopting agile scrum methodology in public organisations' IT project management, there is a lack of comprehensive understanding of these challenges. Therefore, challenges in adopting Agile scrum methodology in public organisations' IT project management context were studied in this literature review. This study aims to report on a systematic literature review about adopting agile scrum methodology in public organisations' IT project management and provide empirical evidence about its current situation and challenges. This research has used a systematic literature review as a research strategy and thematic analysis to analyse the secondary data, where the analysis is conducted based on the filtered themes, sub-themes and codes. The systematic literature review uses the preferred Reporting Items for Systematic Reviews and Meta-Analyses (PRISMA) framework; inclusion and exclusion criteria systematically assess the quality of chosen papers and either include or exclude them for this research. Most relevant studies for final inclusion were selected, screened, and shortlisted based on the keywords from academic databases and other online resources to investigate and analyse the research question. The implementation of the agile scrum methodology in IT project management can present notable challenges for public organisations. A number of sources have identified these challenges, and a thorough examination of the matter reveals their frequency.

The thesis deals with problems of agile methodologies in the settings of virtual teams. It begins with the description of virtual teams and their models and deals with both theoretical and practical aspects of mutual communication of their team members. The thesis follows with general characteristics of agile approach and their demonstration on representative methodologies. One of them (methodology Scrum) is described in detail in the next chapter and linked with possibilities of its deployment within virtual teams. Practical part of the thesis deals with the design and implementation of a software application that is focused on effective communication support of virtual teams that utilize Scrum. Deployment of this application is discussed within a case study of a real project which team faced problems of agile software development in the settings of virtual team on a daily basis.

The increase of globalization of business led to the creation of global virtual software development teams in which communication plays an important role. The lack of recent studies raises the need to investigate communication in the context of agile and the current Covid-19 pandemic. This study identifies in literature three factors present in global virtual software development teams: technology, culture, and trust. It aims to explore how they influence internal communication. A qualitative method is conducted on a case study by combining data collected from semi-structured interviews and observations. The case study is a global virtual software development team which implemented the agile Scrum methodology. The findings provide a deep understanding of the positive and negative influences of the factors on communication, including their interrelations and context. Some of the main findings are: (I) the best set up for collaboration among global team members is the combination of synchronous and asynchronous communication through technological tools, (II) cultural diversity leads to differences in the ways members communicate, (III) trust is the precondition of working collaboratively and communicating effectively, (IV) global team members need to occasionally have in-person interactions to nurture their interpersonal relations, (V) the agile Scrum methodology influences internal communication positively, (VI) each communication factor is influenced by time; thus, the theoretical framework developed for this study is updated with this addition, (VII) the Covid- 19 pandemic affects communication to a certain extent.

Nowadays, the business world is characterized by complexity since market and customer requirements are changing rapidly. Based on this assumption, providers are facing the challenge of delivering software products in shorter terms while these products remain innovative. Agile software development has a huge impact on how software is developed worldwide and promises business value in short iterations. At the same time, requirements are the base of all software products, and consequently, Requirements Engineering (RE) plays one of the most important roles in system development. Traditional techniques referring to intended data do not cover the constantly increasing demands of RE and unintended data from digital sources has amplified the need for Data-Driven Requirements Engineering (DDRE). This study contributes to Computer and System Science by providing a process to combine DDRE and traditional RE approaches in Agile software development methodologies. In this study, the researcher is trying to provide a concrete solution to the lack of an effective process to address data-driven requirements in a Scrum environment organized by regular Sprints and the purpose of it is to suggest a new method for requirements elicitation based on digital data and combine them with traditional stakeholder-driven RE in a Scrum agile environment. The method intends to assist Agile professionals to elicit requirements from digital sources in combination with intended data derived from the stakeholders without impacting the main Agile practices. The approach to conduct this study is Design Science Research (DSR) and contains five steps: Explicate Problem, Define Requirements, Design and develop Artefact, Demonstrate Artefact, and Evaluate Artefact. Literature review has been conducted to explicate the research problem and define the requirements of the artefact. Then, a process and a collaboration board have been created based on the requirements to bring DDRE and traditional RE into the Scrum environment. The researcher performed a demonstration of two illustrative cases of the usage of the proposed artefact to three Scrum professionals and three semi-structured interviews were conducted to evaluate the artefact. After the evaluation, the researcher refined and presented the final artefact that will help the public and private organizations to reduce the costs and time plan on eliciting requirements, and to increase the customers’ satisfaction. The artefact has not been applied in a real Agile environment, but Requirement Engineers and Agile team members can build on the proposed method and bring the elicitation approach of DDRE closer to the software development process.

Цель командной работы – создание игры «Симулятор Владельца Продукта». Цель личной работы – разработка игры «Симулятор Владельца Продукта» с использованием современных инструментов разработки. Объект исследования – компьютерные игры. Методы исследования: анализ современных инструментов разработки игр, генерация идей для лучшей реализации игры, программная реализация игры, её тестирование на наличие ошибок, проведение апробации игры на 30 пользователях, сбор и систематизация обратной связи. В результате командной работы создан продукт «‎Симулятор Владельца Продукта» – это компьютерная игра, доступная в браузере. Результатом личной работы является разработанная игра, доступная в браузере, описание реализованных сцен и скриптов. Выпускная квалификационная работа выполнена в текстовом редакторе Microsoft Word. / The goal of teamwork is to create the game “Product Owner Simulator”. The goal of my personal work is to develop the game “Product Owner Simulator” using modern development tools. The object of research is computer games. Research methods: analysis of modern tools, game development, generating ideas for better implementation of games, software implementation of games, testing them for errors, testing the game on 30 users, assembling and systematizing feedback. As a result of the team’s work, the product “Product Owner Simulator” was created - this is a computer game available in the browser. The result of individual work is a developed game, available in the browser, a description of the implemented scenes and scripts. The final qualifying work was completed in the text editor Microsoft Word.

Была выявлена проблема высокого порога вхождения в роль владельца продукта. Поставлена гипотеза, что если разработать механику игры, приближенную к задачам Владельца Продукта в реальной жизни, то в игре можно будет пройти практику в роли Владельца Продукта для приобретения опыта. Общей командной целью было создание игры «Симулятор Владельца Продукта», а цель личной работы – определение направления развития игры как продукта. Результатом личной работы является описание механики игры в виде схем, бэклог продукта в виде пользовательских историй и требований, и статистика обратной связи от пользователей по результатам проведенных опросов. По статистике всего было порядка тысячи игровых сессий и положительная обратная связь от игроков. / The problem of a high threshold for entering the role of product owner was identified. It is hypothesized that if we develop game mechanics that are close to the tasks of a Product Owner in real life, then in the game it will be possible to practice as a Product Owner to gain experience. The overall team goal was to create the “Product Owner Simulator” game, and the goal of personal work was to determine the direction of development of the game as a product. The result of personal work is a description of the game mechanics in the form of diagrams, a product backlog in the form of user stories and requirements, and statistics of feedback from users based on the results of surveys. According to statistics, there were about a thousand gaming sessions and positive feedback from players.

La presente tesis posee un enfoque cuantitativo no experimental de diseño correlacional cuyo objetivo general es determinar si la metodología ágil Scrum se relaciona con la satisfacción del cliente de aplicativos móviles de las principales entidades bancarias declaradas transformadoras digitales en la sección de banca minorista en Lima Metropolitana en el 2019. La metodología ágil Scrum y la satisfacción del cliente son temas de gran impacto, los cuales se desarrollan de manera constante en diversas industrias en el mundo, encontrando zonas inexploradas en cuanto al conocimiento de la relación de ambas variables. En consecuencia, podrían mejorar las metodologías de trabajo en el mundo laboral, así como la experiencia del cliente o usuario final. La investigación se realizó sobre una población de 2,371,542 personas, representados por una muestra de 383 personas, de quienes se recolectó información a través de una encuesta conformada por dos apartados, el primero se enfoca en la variable metodología ágil Scrum, estuvo compuesto por 17 preguntas y se adaptó del artículo “The Impact of Scrum on Costumer Satisfaction An Empirical Study; respecto al segundo apartado, se focalizó en la variable satisfacción del cliente, constituido por 27 preguntas y adaptadas, principalmente, de la herramienta de medición SERVQUAL. De esta manera, ambos apartados de la encuesta fueron llevados al contexto del rubro financiero y validados por jueces expertos, obteniéndose, finalmente un total de 44 preguntas de tipo Likert. Para la relación entre variables se utilizó la aplicación de la estadística no paramétrica, haciendo uso del estadístico Chi-cuadrado y la prueba estadística Rho de Spearman. Los resultados presentan r = 0,68 comprobándose que existe una relación directamente proporcional entre las variables. Asimismo, a un nivel de significancia α=0,05 se obtuvo un p = 0,000 (< 0,05) menor al nivel de significancia, demostrando la existencia significativa de una relación media entre la metodología ágil Scrum y la satisfacción del cliente, sugiriendo a los actores claves de los escenarios afines tomar en cuenta que las modificaciones de aplicaciones móviles desarrolladas con la metodología ágil Scrum impacta en la experiencia del usuario. / This thesis has a non-experimental quantitative approach of correlational design whose general objective is to determine if the Scrum methodology is related to customer satisfaction of mobile applications of the main banking entities declared digital transformers in the retail banking section in Metropolitan Lima in 2019. The Scrum methodology and customer satisfaction are high-impact topics, which are constantly being developed in various industries around the world finding unexplored areas regarding the knowledge of the relationship of both variables. Consequently, they could improve work methodologies in the world of work, as well as the client or end user experience. The research was conducted on a population of 2,371,542 people, represented by a sample of 383 people; this information was collected through a survey composed of two sections, the first one focuses on the Scrum methodology variable, it was composed of 17 questions and was adapted from the article “The Impact of Scrum on Costumer Satisfaction An Empirical Study”; regarding the second section, it focused on the client satisfaction variable, composed of 27 questions and adapted, mainly, from SERVQUAL. In this way, both sections of the survey were taken to the context of the financial sector and validated by expert judges, finally obtaining a total of 44 Likert-type questions. The application of non-parametric statistics was used for the relationship between variables making use of the Chi-square statistic and the Spearman's Rho statistical test. The results show r = 0.68 verifying that there is a directly proportional relationship between the variables. Also, the results show that for a level of significance α = 0.05, it is p = 0.000 (<0.05) lower than the significance level was obtained demonstrating the significant existence of an average relationship between the Scrum methodology and customer satisfaction, suggesting to the key actors of the related scenarios take into account that the modifications of mobile applications developed with the Scrum methodology impact the user experience. / Tesis

Проведен литературно-аналитический обзор по следующим направлениям поиска: проблемы и предпосылки изменений в сфере ЖКХ и инновационные модели САРТ, применение новых технологий в задачах оптимизации деятельности управляющих компаний; Разработан бизнес-план и сопутствующая документацию к внедрению новой методологии. Произведена оценка экономической эффективности проекта; Рассмотрены возможные пути расширения системы автоматического регулирования температуры. / A literature and analytical review was conducted in the following areas of search: problems and prerequisites for changes in the housing and utilities sector and innovative models of SART, the use of new technologies in the tasks of optimizing the activities of management companies; A business plan and related documentation for the implementation of the new methodology were developed. The economic efficiency of the project is evaluated; possible ways of expanding the automatic temperature control system are considered.