Evaluating the role of scrum methodology for risk management in information technology enterprises

This study aims to evaluating the Scrum methodology's effectiveness in risk management techniques in Oman, Iraq, and Qatar. Businesses in Oman, Iraq, and Qatar discuss management in terms of the scale of their operations and the influence of risk management has on the success of information technology efforts. This research focuses on information technology firms and technical projects. Investigated them to get a full comprehension of the underlying premises of the postulation. Risk management as a technique is fraught with peril. This makes determining if risk management is an appropriate strategy for managing and managing risks in the IT manufacturing process difficult. The study shows how the Scrum framework is used to execute risk management in IT organizations. Quantitative research was used to collect data for this study. The sample consists of 150 employees from different IT businesses. Collecting data via the use of standardized tools (questionnaires). The researcher conducted an online survey using Google Forms. The aim of this research is to determine the influence of the scrum approach to risk management in enterprises (information technology projects).to achieve higher performance and more efficient energy management. Implement innovative risk management tactics based on technology. Findings The data show that most employees are adjusting to the new scrum management strategy they have used at work, with the majority reporting feeling at ease with the new system. (53, ,56 percent are signatures, 70, percent) Adopt the scrum method throughout the project's life cycle. Technology adoption in the workplace to adapt to rapid changes in energy management systems and varied government laws encouraging energy saving. Employee training and flexibility in dealing with programs that have the potential to disrupt the process assist achieving the goals. Restructuring projects firms to optimize their energy and overall performance.


Introduction
Scrum, methodology, Scrum is an iterative and methodical method for project management that is structured around an "inspect and change" philosophy. Scrum is used to spread the software in intervals called "Sprints" (usually 3-6-week iterations). [3] A sprint starts with planning and concludes with evaluation. A sprint preparation meeting is a time-restricted conference call dedicated to developing a detailed sprint calendar. Project partners attend sprint assessment meetings to assess the company, the industry, and technology. A retrospective meeting may be scheduled to examine completed sprints. A daily Scrum meeting is a brief daily meeting (often up to 15 minutes long) during which each team member must answer three questions: What did I do yesterday? What am I going to accomplish today, and how will I overcome the obstacles that stand in my way? It created 2 A. M. Younus and M. Abumandil: Evaluating the role of scrum methodology for risk management in information technology enterprises three components: product backlogs, sprint backlogs, and burn down charts. Backlogs comprise company-specific criteria, while normal burn down maps depict the remaining work. The risk of using Scrum in global application development: they often considered Scrum beneficial for colocated projects with small team sizes. Scrum teams are self-organizing and are built on collaboration and coordination amongst diverse teams. However, project shareholders' allocation to initiatives is also diversified by physical, geographical, and sociocultural differences [4]. It creates a slew of complications or threats that might stymie cooperative and collaborative operations. Such project structural elements as coordination, increased number of sites, engagement of many project personnel, and lack of tool support may all have a significant impact on a project's interaction mechanisms. However, we would argue that individual project concerns would introduce several impediments or hazards that would obstruct the usage of Scrum. By gaining a grasp of the project's context, you may begin practicing Scrum. Examine: The goal of the published analysis was to identify and appraise the issues or risks that must be considered while implementing Scrum in projects, as well as supplementary approaches for mitigating these risks, as documented in the academic literature. We conducted a Comprehensive Literature Review to categorize the key articles addressing the use of Scrum, which involved a variety of tasks, including the development of a review procedure, the identification and collection of primary documents, data analysis and synthesis, and documentation of the findings[3] [4]. Ours specified twenty main studies that examine the utilization of Scrum activities. You will discover a comprehensive summary of our observations, including all of them. To mitigate these risks, we assess the primary issues or hazards as well as supplementary measures. Our findings are organized logically, as any realistic observation is expected to do. Denotes: Research Issues. Is there a correlation between the success of information technology projects and risk management? " To provide a complete answer to the research question, this research aim establishes the objectives for this study, which are to investigate the risk management strategy in the Scrum context often employed in information technology projects. My interpretative study aims to elucidate the risk management process in a Scrum environment Provide a feasible solution by using the scrum methodology. The following are the specific objectives of the problem: ➢ Rapid implementation of high-quality tasks in a timely way ➢ Resolving logistical and organizational issues for the team. From developers and project managers.
➢ Modification of the working style to a more contemporary appearance.

Literature Review
A. Scrum development and project management to provide critical consistency in an oftencomplicated project delivery strategy, the Scrum organization defines tasks, responsibilities, and meetings. Scrum is well-known for its fast-paced Sprints, during which they deliver an MVP every two weeks [4]. The Kanban method: By visualizing their workflow, limiting work in progress (WIP), and enhancing the flow of backlogged items, Kanban enables more traditional businesses to improve their operations. [5] Kanban is the Japanese phrase for "visual sign" or "note." Extreme Programming (XP): XP emphasizes application quality and adaptability to changing client expectations. Pair programming, comprehensive code updates, and unit testing characterize this Scrum method. Adaptive System Development (ASD): ASD is most recognized for its repeated three-phase development phase. FDD is a lightweight Scrum approach that blends a variety of industry best practices into a five-step implementation cycle. The development cycle generates the overall idea, the timetable by feature, the idea by feature, and the build by feature [5] [6] [7].
B. Risks in performing Projects and the Scrum Framework Mode of Team Coordination For projects with minimal risk or ambiguity, they offer an impersonal coordination mode; for projects with moderate levels of uncertainty, it offered a personal coordination mode; and for projects with elevated levels of uncertainty, a group coordination mode is recommended. [14] External and internal integration, organized planning, and institutional oversight in terms of the intrinsic risk of a project, which is affected by the project's scale, technological expertise, and layout, several types of projects require distinct management resources to implement risk management countermeasures. [14] For low project risk or confusion, use arm's length relationships between parties involved.

Methodology
The researcher will use a descriptive research design and will collect data from various government and business institutions that use a work-from-home plan for human resource management. There are 150 people that responded to an online survey. Questionnaire for a survey created using Google forms and the researcher will use a quantitative approach [ The researcher has distributed to Enterprises As a consequence, the population research is segmented by firm and total staff count of 150 at (Oman, Iraq, and Qatar), ( In this analysis, the frequency distribution was used to determine the characteristics of the respondent profile. In relation to the current study, data was gathered from 150 respondents. Have been asked about demographic information: here are gender, age, ethnicity, and current study. (Table.2)

Result
In Figure 1, the diagram depicts the primary benefit of using the scrum model in small and mediumsized business firms, which is risk reduction during development. 56.1 percent believe that establishing a scrum model will assist the company and teams in completing the project successfully. It is used by Scrum teams to structure their product development efforts. A scrum master manages the team's overall process, while developers and product owners collaborate with the business to understand requirements. Managing medium and small scrum teams can help reduce meeting time and boost productivity. In these instances, the team may wish to consider adopting a scrum methodology. This technique subdivides larger scrum project teams into smaller scrum project subteams. Additionally, some believe that implementing the scrum model in a business can accelerate development by 12.1 percent in terms of organization and management. According to the survey depicted in Figure 2, not all respondents agreed that the scrum model should be adopted by small and medium-sized businesses. Because adoption requires some pre-adoption strategies, 59 percent of respondents selected the three factors that could result in failure or success. According to our research, managers are hesitant to adopt scrum in business firms because it requires a staff with sufficient knowledge and experience from various companies to apply. Additionally, some believe that even if the company adopts the scrum model, they will fail because it will suspend some of their projects until the team demonstrates the ability and skill to complete them. It is clear from our respondents' responses that they do not believe that perceived limitations associated with scrum approaches, such as a lack of formal guidelines, insufficient rewards, or an increased risk of project failure, are inhibitors of their adoption and use (see Figure 3). Rather than that, they attribute difficulties with scrum development acceptance to organizational resistance and managerial disinterest. Lack of training and peer support are also identified as challenges, adding to the view that organizational actions, at 53.3 percent, are probably the most significant impediments to the adoption and diffusion of scrum practices. Our respondents provide additional context by identifying scrum ignorance, a lack of pair programming facilities, individual resistance, and an exclusive reliance on economic evaluation criteria as additional barriers to scrum methods adoption. In Figure 5, we ask respondents if their company uses any type of risk management process and discover that 70.6 percent do. The remaining 28.9 percent do not apply, as most small businesses do not survive for an extended period.

Finding
The case, review, risk management, and evaluation of the organization were thoroughly analyzed. The researcher used Google Forms to create the survey questionnaire and took a quantitative approach. A method for compiling and interpreting the following data: 53,56 percent support scrum methods for the best business life cycle management, 70,73 percent support agile methods for risk management in small and medium-sized enterprises (SMEs).

Recommendations for Further Studies
The Figure 7 is suggested as an implication. (scrum conceptual framework secure methodology for the development of information technology) conceptual model and evaluation of information technology companies, study and development of the state of risk management processes using the scrum model, and, in exceptional cases, to serve as the context for small-scale investigations. Companies debate management strategies based on the size of their respective businesses and the role of risk management in the success of IT projects. The validity of the method design will be determined through mixed-methods or qualitative research [10]. The second approach is a structured questionnaire distributed to various project stakeholders across multiple organizations in the public sector and the information technology industry [12] [13]. Smart pls, SPSS and structural equation modelling (SEM) will be used to analyze the collected data and establish structural relationships between scrum factors. scrum conceptual framework