Implementation Of Scrum Research Articles

GAME DEVELOPMENT PROJECT MANAGEMENT USING SCRUM FRAMEWORK: HYPERCASUAL GAME CASE STUDY 'RUSH RUNNER'

The research aims to explore and implement an effective Project Management approach in Game Development using the Scrum Framework. A case study was conducted on the development of a hypercasual game titled "Rush Runner." With a focus on rapid iterations, continuous feedback, and adaptation to changes, the Scrum methodology was used to manage the game development workflow from planning to publication. Concrete steps were taken to adapt to user needs and evolving demands as an integral part of the development process. The research findings indicate that the implementation of Scrum had a positive impact on productivity, quality, and user satisfaction in hypercasual game development. Furthermore, the integration of Project Management and the Scrum approach optimized overall time, cost, and quality. These findings provide valuable insights for practitioners and researchers in the field of game development to understand the importance of an adaptive and responsive Project Management approach to market changes and user needs.

Evaluation of Scrum Implementation and Recommendation Improvement in Software Development: a Case Study of Logistic Company XYZ

PT XYZ provides a digital platform for the national logistics ecosystem and is connected to a global network. PT XYZ applies Agile as a project management methodology so that each team member can focus on continuous improvement and delivering value to customers. The framework used is Scrum during software development to complete work in Agile. However, there are problems during software development, such as failing to meet the targeted deliverables. This research evaluates the implementation of Scrum in PT XYZ and provides recommendations for improving the software development process using Scrum Evaluation Metrics based on Scrum Guide 2020 and Essentials Scrum. The research utilized mixed methods, combining quantitative data collection through questionnaires with qualitative methods involving interviews with Scrum Master and stakeholders, followed by a review of company documents. The result was processed using the Agile Maturity Model's Key Process Area (KPA) rating. The research shows that overall, the KPA rating value of 87.39% is interpreted as Fully Achieved. Recommendations for improvement focused on 27 recommendations for 61 practices that were not Fully Achieved, with high priority given to 15 recommendations. This evaluation and recommendation aim to improve the implementation of Scrum in PT XYZ and overcome the problem of backlog targets not being achieved in the Fulfillment squad.

Implementation of Scrum for Developing the Data Visualization Dashboard for the PLN UP3 Yogyakarta Project

Implementation of Scrum for Developing the Data Visualization Dashboard for the PLN UP3 Yogyakarta Project

Recommendation for Scrum-Based Software Development Process with Scrum at Scale: A Case Study of Software House XYZ

Software House XYZ employs Scrum as one of its software development processes. However, the company faces several challenges in the implementation of Scrum, leading to delays in its product releases. Two specific problems are the control of a large-scale Scrum team and the management of team commitments. To address these issues, the Scrum at Scale framework has been chosen as a solution. Before implementing Scrum at Scale, an assessment of the current Scrum maturity level at Software House XYZ is deemed necessary. The Scrum Maturity Model, adapted to the Scrum Guide 2020, is selected as the method to evaluate how effectively the company is implementing Scrum. A questionnaire comprising 81 practices was distributed to development teams, with 10 valid responses collected. Based on the assessment using the Scrum Maturity Model, the current Scrum implementation maturity at Software House XYZ is rated at level 1, Initial. A total of 61 practices are proposed for improvement in the Scrum process. Scrum at Scale can be implemented once the suggested Scrum process improvements have been made. These recommendations are structured following the framework outlined in the Scrum at Scale Guide 2022. The validation of the Scrum-at-Scale recommendations was conducted by us through interviews with representatives from Software House XYZ. From the validation results, the company expresses interest in trying to implement Scrum at Scale. However, the company agrees to enhance the existing Scrum process within the organization before fully adopting Scrum at Scale.

Implementation of Scrum in the manufacture of non-invasive blood sugar detection devices using PPG signals

This study presents the effective integration of Scrum methodology in the production process of non-invasive blood sugar testing devices using Photoplethysmography (PPG) signals. During three months, a team consisting of a Product Owner, Scrum Master, and Developer Team successfully utilized Scrum's agile structure to manage the challenges of PPG signal processing, hardware integration, and software development. The repeated sprint cycles enabled swift adjustment to new obstacles and stakeholder input, guaranteeing both effectiveness and agility in the development process. The dynamic approach facilitated both the punctual delivery of complex medical equipment and the cultivation of a culture focused on ongoing enhancement, establishing a model for the future use of agile approaches in healthcare technology. The successful implementation highlights the effectiveness of Scrum in managing the complexities of medical device development. It provides a model for improving non-invasive blood sugar detection devices and establishes agile methodologies as a key driver of innovation in healthcare technology.

Using the Scrum Method to Developing Population Information System

The adoption of Population Information System is crucial to enhance work effectiveness and serves as a manifestation of transparency in population data management. The complexity from design to implementation of such a population information system poses its own challenges. There are at least three main issues in system design, namely time estimation, team management, and ensuring the quality of system being developed. These issues must be addressed early on to prevent potential team management problems during the design and development stages of the application. One suitable method that can be employed for the design of the population information system is the Scrum methodology. Scrum is a software development framework that emphasizes a collaborative and adaptive approach. It falls under the Agile methodology, aiming to produce products that are more responsive to changes and enabling teams to adapt quickly in a dynamic environment. Scrum also promotes transparency in the development process, aiding in monitoring system progress and information accuracy. Compared to the commonly used Waterfall method, the Scrum approach offers greater flexibility in dealing with changes in requirements or needs that may arise during the development process. While the Waterfall method tends to follow predefined in linear steps. The novelty of this research lies in the proactive approach to addressing the complexity of designing population information systems by implementing Agile methodologies such as Scrum. Thus, it is expected that the implementation of Scrum will bring significant changes in improving the effectiveness and transparency in the development of population information systems.

Onboarding Model to Integrate Newcomers into Scrum Team at an Insurance Company

PT XYZ applies the Scrum framework to meet application’s user demands quickly. The average percentage of IT employee turnover that occurred at PT XYZ from 2020 to 2022 was 14.5%. Every time a company recruits a new employee, the company must help that employee to adapt the Scrum method used for the company's system development process. However, PT XYZ information technology division does not yet have a specific onboarding method to help new employees adapt to the implementation of Scrum effectively without disrupting the ongoing sprint. Qualitative methods are used in the case study to collect data from a hybrid working Scrum team through interviews. The interview data was analyzed thematically with a determined model from an existing onboarding theory. Onboarding practices and adjustments are described and delivered consisting of onboarding activities, newcomer adjustments, and workplace adjustments. A combination of general and specific onboarding practices related to agile helps the successful onboarding of new members to a Scrum team. A practical guide is also described to improve successful onboarding practices into Scrum teams.

Pengembangan Portal Penjualan Lobster berbasis Web menggunakan Metode Scrum dengan Fitur Prediksi Harga menggunakan Regresi Linier Berganda

This research aims to reveal effective design and content strategies to enhance the attractiveness of a website-based lobster export sales portal. These strategies are developed to capture attention and maintain buyer interest while integrating a one-month forward price prediction feature using linear regression. The research methodology involves implementing the Scrum method for website project management and multiple linear regression to forecast lobster prices. The focus lies on Scrum implementation in designing the sales portal and incorporating lobster price prediction features on the website. The research results demonstrate the successful development of the website using the Scrum framework within three sprints. Feasibility testing with Blackbox Testing aligns with expectations. Multiple linear regression is utilized to predict lobster prices, yielding a forecasted price of 587.3 for the 57th month. With a changing formula each month, the model aims for greater accuracy in anticipating lobster price fluctuations related to seasonal dynamics and specific events. This research provides insights into the implementation of Scrum in website design and practical applications of lobster price prediction in the context of export sales.

Scrum Maturity Level Evaluation and Improvement Recommendation: Case Study on ABC Application

Bank XYZ, one of the digital banking in Indonesia, has a digital product ABC for customers to complete online banking transactions. Bank XYZ uses Scrum as the methodology to develop ABC. Several problems were found in the process related to the delay in the release process. The achievement of sprint goals from May to December 2021 is only 6%. This fact allegedly caused some frequent release delays. To resolve the root causes, mixed-method research was conducted to provide recommendations for improving the implementation of Scrum. The Scrum Maturity Model questionnaires were distributed to several Scrum teams, followed by interviews with several roles that were used to validate the results. The key process area rating formula of the Agile maturity model was used to decide the maturity level. After the maturity level result was obtained, recommendation practices were generated from the not well-implemented practice. This case-based research shows that Bank XYZ reached maturity level 2 for ABC development. Bank XYZ has implemented 78 out of 79 practices, however, 28 practices need improvement and one practice needs to be applied. Objectives of maturity levels group recommendation practices. The combination of Scrum best practices and empirical practices from previous research generated those practices. This research was intended to give general recommendations on how to improve Scrum implementation and on how to resolve release time problems by enhancing Scrum in Bank XYZ empirically.

Analysis of Level Team Effectiveness in The Implementation of Scrum Using Evidence-Based Management (Case Study: Company A as A Fintech Industry)

Analysis of Level Team Effectiveness in The Implementation of Scrum Using Evidence-Based Management (Case Study: Company A as A Fintech Industry)

Analysis of The Implementation of SCRUM in The Development of A BBLobster Content Management System

PT Rapier Technology International applies scrum in developing the BBLobster Content Management System (CMS). Scrum is a framework for developing an iterative, flexible, and effective BBLobster CMS designed to deliver significant value quickly. This study aims to identify the problems encountered in scrum implementation and validate the factors that influence the interaction with Scrum adoption during the BBLobster CMS development process using variable measurements. The measurement variables are the team factor variable, individual factor variable, technology factor variable, organizational factor variable, and scrum adoption variable. They analyzed the measurement of the data model (outer model) and structural model (inner model) using SmartPLS 3.0 after data collection using a questionnaire via google forms. The results of this study show that the analysis of the structural model test conducted by knowing the value of R-Square (R2) is a team factor variable, individual factor, technological factor, and organizational factor that has an influence of 67.4% on scrum adoption.

How do Scrum Methodologies Influence the Team's Cultural Values? A Multiple Case Study on Agile Teams in Nonsoftware Industries

The cultural component of the project team is recognized as one of the most critical factors in the implementation of agile project management (APM), especially in nonsoftware industries, where the diffusion of APM still involves several challenges. Particularly, the successful implementation of scrum—the most diffused APM methodology—seems related to the project teams’ subculture, which may differ from the overall organizational culture of the company. This article contributes to the APM literature in nonsoftware contexts by studying the cultural values that develop inside agile teams and the scrum principles and practices that are particularly relevant for fostering these values. Using interview data collected from seven manufacturing and service organizations, we use the competing value framework as the theoretical model to understand the cultural profiles of their organizations, how they deploy into the project teams’ subculture, and what, if any, connections exist with the adoption of scrum principles and practices. We find that clan and market values are the dominant subcultures in agile teams. These cultural values are fostered at a strategic level by a subset of scrum values (i.e., courage, openness, and respect) and pillars (i.e., transparency and adaptation). At an operational level, retrospective meetings and the definition of particular artifacts also contribute to develop these dominant cultural values.

Agile project management for design-build construction projects: a case study

Despite the rising relevance of Design-Build as a favored project delivery method in the United States, no notable change has been observed in how these construction projects are managed, and the Waterfall Project Management method continues to be used as the preferred method of managing these projects. The applicability of Agile Project Management methods to the management of construction projects with Design-Build as a project delivery method has yet to be ascertained. Can Scrum, one of the Agile Project Management frameworks, be effectively used in managing a Design-Build construction project during the design and the construction phase? This study covers the adaptations necessary to apply Scrum to a Design-Build construction project and conducts a case study where Scrum was applied to part of a Design-Build construction project. The outcomes from this study show that the implementation of Scrum in a Design-Build construction project potentially leads to better cost and schedule control, along with superior communication amongst multiple stakeholders. This study is vital to advance knowledge about the applicability of Agile Project Management methods in other Design-Build construction projects during both the design and construction phases. Further research can be conducted by scaling the application of Scrum to a Design-Build construction project for the entire lifecycle.

Analysis of Scrum Implementation in Digital Startup Product Development

One of the renowned methodology to address product development complexity is Agile methodology. Scrum is the tool of Agile methodology which adopts the Agile manifesto through the incremental and iterative way of developing an IT product. It has been widely used for developing a software project in various organizations and has a reputation for effectively managing the process of product development. However, the application of Scrum often adjusted to fit with the organization. The aim of this paper is to understand the implementation and challenges of Scrum through the interview to the Scrum roles. The needs to build a shippable and working product for immediate business testing or user acceptance are reasons that drive the teams to choose Scrum. The methodology used is qualitative research method using an in-depth interview to the scrum roles that involved in IT product development in the digital startup in Indonesia. The result showed that Scrum makes the process of product development more effective, improves coordination between team members and helps the development team to self-independent in doing the task. Therefore, in summarize, Scrum could manage the process of product development well.
 Keywords: Digital Startup, Agile Method, Product Development, Scrum

EvaScrum: An assessment instrument to support the diagnosis of Scrum – results of two case studies

The purpose of the process evaluation is to obtain relevant information in a qualitative and quantitative way about the current state in which a process is to support processes of evolution and continuous improvement. Scrum is one of the most used agile approaches, however, there some aspects that can hinder its implementation, e.g., lack of detail of artefacts and meetings that raises, including the timetables, application of the approach, among others. In this sense, and in order to facilitate the success in the implementation of Scrum, this paper presents EvaScrum, an assessment instrument that provides the opportunity to professionals and consultants to assess and diagnose the degree of implementation of Scrum through questions, metrics, a spreadsheet and a Web application. EvaScrum is based on Mr. Scrum; a reference model which provides a clear and complete set of process elements based on Scrum and EvaScrumTOOL, a web tool to manage the assessments. This paper presents the detailed analysis of two case studies in software development enterprises where EvaScrum was applied. The results obtained have allowed case study enterprises to identify improvement opportunities to carry out in the processes and projects where Scrum is being applied, all this, in a practical, useful and suitable manner which allow these types of enterprises, to assess and diagnose their implementations of Scrum with feasible resources both time and economically.

EvaScrum: An assessment instrument to support the diagnosis of Scrum – results of two case studies

The purpose of the process evaluation is to obtain relevant information in a qualitative and quantitative way about the current state in which a process is to support processes of evolution and continuous improvement. Scrum is one of the most used agile approaches, however, there some aspects that can hinder its implementation, e.g., lack of detail of artefacts and meetings that raises, including the timetables, application of the approach, among others. In this sense, and in order to facilitate the success in the implementation of Scrum, this paper presents EvaScrum, an assessment instrument that provides the opportunity to professionals and consultants to assess and diagnose the degree of implementation of Scrum through questions, metrics, a spreadsheet and a Web application. EvaScrum is based on Mr. Scrum; a reference model which provides a clear and complete set of process elements based on Scrum and EvaScrumTOOL, a web tool to manage the assessments. This paper presents the detailed analysis of two case studies in software development enterprises where EvaScrum was applied. The results obtained have allowed case study enterprises to identify improvement opportunities to carry out in the processes and projects where Scrum is being applied, all this, in a practical, useful and suitable manner which allow these types of enterprises, to assess and diagnose their implementations of Scrum with feasible resources both time and economically.

WHEN WORLDS COLLIDE – A COMPARATIVE ANALYSIS OF ISSUES IMPEDING ADOPTION OF AGILE FOR HARDWARE

AbstractThe objective of this paper is to explore challenges identified for implementation of scrum for hardware development intersect with agile principles found in the literature. A series of comparative analyses are done at the textual level, through logical intersections, and through thematic analysis. It is shown that there are five underlying themes found across two sets of scrum challenges (constraints of physicality and the 13 principles). These five themes include: flexiblity, chunkability, scalability, endurability, and teamability. These five themes further are found related to the defining principles of the agile manifesto. Using this understanding, future efforts will include empirical case study work to determine the impact that these have on application of scrum methods and tools. Additionally, guidelines should be developed to help hardware product engineers in applying scrum.

Scrum Challenges: An Agile Process Reengineering in Software Engineering

Business Process Reengineering (BPR) is an organizational strategy seeking identification of critical factors affecting software development practices in Software Engineering Management (SEM). The agile approaches opened the door of BPR in software development organizations. Dynamically changing technological environment has invited software development organizations, towards adoption of reengineering of strategies and practices. Nowadays, Scrum has been trending as an agile framework for Software Engineering Management (SEM) in software development organizations but considerable research work has not been done with Scrum and its successful implementation yet. The goal of this research is to highlight weaknesses and limitations of Scrum like project level documentation, planning, estimation, progress tracker, CICD etc.; and identification of challenges and issues with implementation of Scrum in software project development like large scaled project in distributed work environment with multiple Scrum teams, organizational structure, lack of knowledge ad awareness about Scrum; using empirical analysis and literature studies. The result of this research will open the door for the next stage of research to overcome the limitation and issues with implementation of Scrum and raise a request of BPR towards focus on improvement in SEM practices in software development organizations by proposing proper training about the empiricism control theory of Scrum that helps organizations in understanding the successful implementation of Scrum and its benefits. This research also raises a question in the form of suggestion that it is good time for a hybrid form of Scrum with other standard agile based frameworks or traditional SDLC methodologies.

Scrumban: An Agile Integration of Scrum and Kanban in Software Engineering

Software Engineering (SE) technologies are emerging day by day and seeking ABPR (Agile Business Process Reengineering) for Software Engineering Management (SEM) frameworks in software development organizations. BPR can enable organizational capabilities to initiate and implement critical change in execution. Under the roof of agile and on the base of empiricism, the Scrum has been proven itself as an ABPR approach for software engineering management in the software development organizations, across the world, by improving productivity, self-organization and collaboration for standard software development processes. Scrum has been leading software project development practices using its own characteristics: Artifacts, Pillars, Values, Events and Roles. But still software project development organizations are facing some issues with their software project development and management processes, like no documentation policy which results into inaccurate estimation, internal states of each work item flowing through the Scrum Board, Sprint tracker and prediction towards goal achievement which can be considered as challenges for Scrum due its limitations as well as Scrum does not allow, any alteration in its rules. Such issues have raised a question against implementation of Scrum and have opened the door for the next level of research to answer the question, how to overcome the limitations of Scrum. Kanban can provide the solution to some of these issues but it can’t provide complete SEM solutions to software Development Organizations. The aim of this research study is empirical analysis about how the formation of hybrid framework Scrumban as an integration of Scrum with Kanban, can resolve challenges of Scrum; using literature reviews, case study reviews, and research surveys; and this research has proposed a conceptual customized Scrumban framework, by keeping Kanban in the center of customization under the bound of Scrum rules. This research also concludes limitations of Scrumban, like project documentation, planning, large scaled project, distributed environment, team capabilities etc.; as each method has its own limitations.

ІННОВАЦІЇ SCRUM У КОНТЕКСТІ УПРАВЛІННЯ ВІТЧИЗНЯНИМ БІЗНЕСОМ

The theoretical and conceptual essence of business management based on the Scrum method is substantiated. Scientific interpretations of the essence, values and principles of Scrum activity management are analyzed and their authorial definition is proposed. The basic stages and specifics of business management based on foreign experience of Scrum are considered. The author's interpretation of the concept of Scrum and the classification of participants of Scrum teams is offered. The classification of the causes of Scrum-bat emergence and the basic criteria of business readiness for full implementation of Scrum are elaborated. The obligation to review, analyze and build business management has been implemented from the point of view of transformation of management processes to the conditions of the modern economy. Emphasis is placed on the need to use the innovative Scrum method in managing the business activities of domestic entities. The scientific value of the results of research lies in directing the results of the work to solve the problem of finding the concepts of effective business management in Ukraine, which will be able to provide flexibility and increase the financial results of business and economic growth in general.