Scrum Master Research Articles

From Backlogs to Bots: Generative AI's Impact on Agile Role Evolution

ABSTRACTThis position paper investigates the transformative impact of generative artificial intelligence (GenAI) on Agile roles. Focusing on the product owner, developer, and scrum master, we analyze how GenAI redefines traditional tasks, encouraging a shift towards more strategic and creative functions. Through practical experience, we illustrate AI's role in enhancing Agile processes, its practices and emphasize the need for Agile practitioners to integrate AI understanding. These results highlight the balance between GenAI's efficiencies and Agile's human‐centric principles, proposing research directions for AI‐enriched Agile practices that promise to drive innovation and maintain the agility in a technologically progressive era.

Large-scale agile security practices in software engineering

Purpose Security in large-scale agile is a crucial aspect that should be carefully addressed to ensure the protection of sensitive data, systems and user privacy. This study aims to identify and characterize the security practices that can be applied in managing large-scale agile projects. Design/methodology/approach A qualitative study is carried out through 18 interviews with 6 software development companies based in Portugal. Professionals who play the roles of Product Owner, Scrum Master and Scrum Member were interviewed. A thematic analysis was applied to identify deductive and inductive security practices. Findings The findings identified a total of 15 security practices, of which 8 are deductive themes and 7 are inductive. Most common security practices in large-scale agile include penetration testing, sensitive data management, automated testing, threat modeling and the implementation of a DevSecOps approach. Originality/value The results of this study extend the knowledge about large-scale security practices and offer relevant practical contributions for organizations that are migrating to large-scale agile environments. By incorporating security practices at every stage of the agile development lifecycle and fostering a security-conscious culture, organizations can effectively address security challenges in large-scale agile environments.

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.

SCRUM METHODOLOGY FOR LEARNING: APPLICATION ON REFRIGERATION COURSE

This paper discusses the applicability of an agile project management methodology called "Scrum" in postgraduate engineering studies, specifically for managing a refrigeration project. The main objective is to convert an educative project into a real-life project with different challenges and objectives. In this scenario, the teacher plays the role of the product owner, who creates a product backlog containing the main requirements for reaching an ultimate goal by groups of students called "development teams." The team leader, or Scrum master, organizes meetings, controls the workflow, and acts as a link between the team and the product owner. Within the Scrum framework, the project is divided into short work cycles of two weeks named "sprints." After each sprint, an intermediate result should be released and reviewed in accordance with the objectives established. This innovative methodology is expected to teach the students many values, such as awareness, focus, commitment, courage, and respect, besides promoting many soft, hard, and metacognition skills inside them.

The Impact of Teamwork Quality (TWQ) on Agile Software Development Team Performance

Purpose: The study examined the extent to which teamwork quality (TWQ) impacts team performance in the Agile software development space in the U.S. and how the TWQ factors (Communication, coordination of expertise, cohesion, trust, mutual support & value sharing) are ranked in terms of importance to team performance Materials and Methods: The study used correlation and regression analysis to determine the degree of the relationship and the effect of the extended TWQ factors on Agile software team performance. Additionally, the study assessed the relative importance of the TWQ factors to team performance. Participants in the study included IT workers from the software development team in U.S. companies with in-house teams using the Agile methodology. Data was collected using an online survey through survey monkey. The data was presented through descriptive statistics and analyzed using regression analysis. Findings: The study found all the extended TWQ factors were strongly correlated to the team performance. The analysis showed that a statistically significance predictive relationship exists between the extended TWQ factors and Agile software development team performance. However, only mutual support and value sharing contributed statistically significantly to the model. Among these factors, mutual support was ranked as the most important TWQ factor in relation to team performance, while trust was ranked as the least. Implications to Theory, Practice and Policy: This empirical study tested and extended the TWQ model on team performance in the Agile software development space in the U.S. for software development teams and how these TWQ factors are ranked in terms of importance to team performance. The findings provide insight to project teams and team leaders, product owners, scrum masters, and project managers about the TWQ model from the perspective of agile software development teams. The findings also address the critical TWQ factors that are needed for building effective and efficient Agile software development teams.

Perancangan Sistem Pelaporan Incident Hack Di Kominfo Lombok Tengah Menggunakan Agile Pendekatan Scrum

The Scrum method is a methodology included in agile software development. Scrum is considered to be able to produce good quality software according to user wishes, can be used in large and small projects, and is easy to adopt changes. The scrum activity stages include product backlog, sprint backlog, daily scrum, sprint review, and sprint retrospective. Roles in Scrum include product owner, scrum master, and development team. Scrum has structured and iterative stages, so that if the product in the first sprint is not sufficient to meet needs, then in the next sprint a system can be developed that is in accordance with user evaluation. The results obtained from Designing a Hack Incident Reporting System at Kominfo Central Lombok Using the Agile Scrum Approach were proven to be able to overcome changes in requirements during the system development phase, producing products that met the wishes of users because they received repeated reviews.

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.

Implementasi Metode Agile Scrum Dalam Perancangan UI/UX Design Command Control Map Service Di PT. Len Industri (Persero)

Implementasi Metode Agile Scrum Dalam Perancangan UI/UX Design Command Control Map Service Di PT. Len Industri (Persero)

The Impact of a Skill-Driven Model on Scrum Teams in Software Projects: A Catalyst for Digital Transformation

Human skills are a critical factor in the success or failure of a digital project. Limited studies have been conducted to identify the industry demand for skills of scrum roles (product owner, scrum master, web developer) and levels (entry, associate, mid-senior). The evaluation of skills over time benefits both decision-makers and associated team members, which leads to successful project completions. The aim of this research is to improve decision making concerning the level-specific skills of selected scrum roles for digital projects. The study identifies major and minor skills, patterns, and relationships between levels, and formulates the mathematical equations as the most important inputs to the skill-driven model’s implementation and evaluation. Both qualitative and quantitative research methods were used to analyse 900 surveyed job advertisements published on LinkedIn in Europe. Descriptive analysis was used to analyse quantitative data while the deductive approach was followed with thematic analysis. There are required skill sets for each level of roles, level-specific skills, industry-demanded skills, and formulas related to the initial and individual skill ratings that are investigated. A new mechanism for evaluation is introduced based on “the time spent with skills”. As a result, the proposed model is implemented by feeding research findings into the Mendix programming platform. The skill-driven model is a decision-support solution in software project management to evaluate skills which assist in assigning the right person to the right digital project. Further investigation on different job portals can help to improve the accuracy of industry standards and reduce the lack of progression skills by overcoming limitations identified in this paper.

Analysis of project management principles with the Scrum framework in systems development

Objective: Demonstrate a case study on project management using the Scrum framework in the development of systems for a public organization. Design / Methodology / Approach: The research method used in the Case Study is an exploratory research with a qualitative approach, through data collection, application of a structured questionnaire to Stakeholders, Scrum Master and Product Owner and analysis of the artifacts generated. Results: The work demonstrated the factors that affect the effectiveness application of the Scrum framework, highlighting bad practices and barriers related to the understanding of business and products, which reduce the ability to deliver quality and value, ineffectiveness of the method application. Research limitations: the number of interviewees in the organization, for further analysis in the case study. Originality/Value: while previous studies focus on the application of the Scrum method in private companies, this paper presents a case study from the perspective of a public organization.

Causes and Mitigation Practices of Requirement Volatility in Agile Software Development

One of the main obstacles in software development projects is requirement volatility (RV), which is defined as uncertainty or changes in software requirements during the development process. Therefore, this research tries to understand the underlying factors behind the RV and the best practices to reduce it. The methodology used for this research is based upon qualitative research using interviews with 12 participants with experience in agile software development projects. The participants hailed from Austria, Nigeria, the USA, the Philippines, Armenia, Sri Lanka, Germany, Egypt, Canada, and Turkey and held roles such as project managers, software developers, Scrum Masters, testers, business analysts, and product owners. Our findings based on our empirical data revealed six primary factors that cause RV and three main agile practices that help to mitigate it. Theoretically, this study contributes to the body of knowledge relating to RV management. Practically, this research is expected to aid software development teams in comprehending the reasons behind RV and the best practices to effectively minimize it.

Perancangan Arsitektur Sistem Informasi Menggunakan Metode Agile Dengan Kerangka Kerja Scrum Pada Pelayanan Instalasi Gizi RSUD. Ciamis

A hospital nutrition service is an inseparable part of other health services in hospitals, besides that nutrition service is an effort to improve the quality of health services for inpatients or outpatients in hospitals. In implementing the Scrum work frame in the architectural design of the nutrition service information system at the Regional Public Hospital Ciamis (RSUD. Ciamis) it is expected to produce products that are in accordance with the client's needs. The stages from preparation (Initialization), making a product backlog, making a sprint backlog to the execution stage of this method indicate an iterative method because it prioritizes product functions. The Scrum framework implements work functions according to its role, namely the Product Owner who is fully responsible for the products that it produces, the Development team is responsible for project work, and the Scrum master is the person who controls so that the implementation of the work does not go out of the rules of the Scrum game. The results of designing an information system with application development, this research uses the scrum framework which is carried out with 3 sprints with the estimated processing time for each sprint as follows: sprint 1 reaches 30 days, sprint 2 reaches 27 days and sprint 3 reaches 30 days. According to the rules of the scrum framework, each sprint should not exceed one month so that the project can be implemented quickly and produce the desired results

AMANDA (Your Plant Monitoring Application) Implementation Android Application Program Project Management Using Agile Scrum Method and Trello

Software development is closely related to several Software Development Lifecycle (SDLC) processes. PT Inamas Sintesis Teknologi (INASTEK) is committed to helping employees work easier through Internet of Things (IoT) based technology. This research aims to manage a project for making your Plant Monitoring Application (AMANDA) which can be accessed via a smartphone. This research method uses agile scrum which can adapt to user needs which can be developed repeatedly and the Trello application as an archive of sprint data for each division. The results of this study are the AMANDA application which is able to monitor and control strawberry plants in real-time which is equipped with a menu of temperature, humidity, ec meter, ph meter, water level, soil moisture, liquid temp, co2 level, water pump, nutrient pump, pump pH, sample pump, plant pump, and pipe valve with 3 second delay. Work on this application development project with a duration of 3.5 months and a total cost of Rp. 13,999,891 involving PT INASTEK as product owner, Product Management Division as scrum master, and Engineering Division as development team. With the AMANDA application, it can help PT. INASTEK in developing the projects they have.

Navigating cultural resistance:

Objective: This article presents the application of an agile and cultural transformation framework to mitigate the impact of implementing agile methods in an environment of cultural resistance within organizations. Methodology: Product Owner and Scrum Master training were carried out, totaling 62 employees. We used semi-structured interviews with open questions, and a questionnaire with 93 questions was applied to diagnose the level of agile knowledge. In addition, there was detailed documentary research, which involved managers and consultants from the business area and project managers, in addition to the profiles that comprise the agile teams considered. Results: We point out that implementing agile methods in organizations lacks adequate planning. The proposed agile and cultural transformation framework with its various stages, “Training,” “Adapting,” “Monitoring”, and “Evaluate,” was implemented in a large mobile telecommunications company. The framework was presented in detail and represented schematically. Originality: This technological article contributes by bringing practical guidance on implementing agile methods in environments with a different culture, with a low degree of Cultural Fit, reducing cultural resistance and reaping benefits more quickly throughout the change process. We point out that implementing agile methods in organizations lacks adequate planning. The proposed agile and cultural transformation framework with its various stages was implemented in a large mobile telecommunications company. The framework was presented in detail and represented schematically. This technological article contributes by bringing practical guidance on implementing agile methods in environments with a different culture, with a low degree of Cultural Fit, reducing cultural resistance and reaping benefits more quickly throughout the change process.

Case study on evolution performance of agile scrum software development life cycle for shopping cart applications

This paper presents the novel agile scrum methodology for the shopping cart product. The existing software development life cycle, such as waterfall, iterative methods, and spiral life cycles, has a larger failure ratio and cost factors when a connected component fails during the execution of a product. In this paper, we devise a novel agile scrum methodology where sprint backlog and product backlog process are demonstrated with the cost and failure efficiency. The role of the scrum master, standard deviation, mean and completion and task progression are illustrated in the methodology as shown in the result discussion.

CHOOSING METRICS FOR SOFTWARE DEVELOPER’S SCRUM TEAMS

Background. There are many books about software development, slightly fewer books about software development team’s management, and very little about work metrics of software development teams. Existing developers scrum team metrics definition practices were analyzed in this article and common rules were proposed. Application of the rules will allow implementing the Pareto principle in the choosing and using of metrics in developer’s scrum teams.
 Methods. General scientific methods such as the analysis of Russian-language and foreign thematic literature, comparative analysis, induction and analogy were used.
 Results. The result of the article is an ordered action plan, using of which makes it possible to most effectively evaluate the work of the developer’s scrum team. The target audience of the article is wide. Managers of different levels (from the team manager or scrum master to the head of the department) can use the described approach to create metrics for their departments. Developers will be able to better understand how managers see their work and take this into account in their work.
 Conclusion. Software developer typical tasks are divided into technical stages. When allocating metrics to evaluate the effectiveness of each stage, the risk of local optimizations increased. In addition, if the area of responsibility of the manager shifts from the whole to the part, from the efficiency of the company to the efficiency of the business unit, then the risk of choosing the wrong metrics increases many times. Metrics that evaluate a partial result are considered incorrect – they relate to a part of the functionality, a division within the company, etc. As a result, the likelihood of making a management decision in accordance with the interests of the division, rather than the company or the product as a whole, increases. For this reason, the use of private metrics should be avoided.

EVALUATION OF COMPUTER SCIENCE STUDENTS' WORK ON IT PROJECTS BASED ON QUANTIZATION OF PROFESSIONAL ACTIVITY

The article examines the process of evaluating work on IT projects, which is presented systematically and multidimensionally, as a reflective and analytical toolkit. The research was conducted on the basis of the application of a system of humanitarian, psychophysiological, anthropological and informational methods and approaches, where the application of the theory of functional systems and through methodological and value understanding of pedagogical and production experiences and practices are decisive. This work updates the methodological potential of the idea of professionalization, in particular, a specialist in computer specialties, pedagogical anthropology and the theory of functional systems, including the concept of quantization of mental activity, which is interpreted as quantization of professional activity. A decisive methodological and practical-technological factor, which is a prerequisite for considering the evaluation process as a reflective and analytical toolkit, is the systematic quantization of professional activity, which is implemented on the basis of the use of the methodologies of Kanban, Agile methodologies, in particular, Scrum, "Manifesto for Agile Software Development". The research used Information technologies: Jira Software, in particular the Kanban template, Agile tools for Kanban, Agile tools for Scrum. Current strategies for quantifying professional activity when working on IT projects are: Epic; Story; Task; Sub-Task; part of the Story/Task; Bug; Sprint. Students were divided into small groups that worked on IT projects. In the process of project activity, they performed the following roles: Engineer, Scrum Master, Product Owner, Tech Lead. The evaluation presented in the specified system format is a significant component of the result-target basis of work on IT projects, and is also considered as a tool of innovative activity and a prerequisite for personal and professional development and professional communication. In further research, it is planned to develop the problems of professional activity for work on IT projects, which includes the study of motivational, value, cognitive, operational, reflective, components, as well as the use of quantization in pedagogical research on the professional training of students of computer specialties. The results of this study are planned to be applied to improve the qualifications of information technology specialists in the conditions of postgraduate education.

Implementation of Scrum Framework Agile Method to Develop Integrated Asset Management Information System at Universitas Diponegoro Inventory Module

Diponegoro University Property (BMU) requires an inventory process by the assets and logistics division at least once every five years. The inventory process is still manually. So it is necessary to develop an Integrated Asset Management Information System Inventory Module. The development of an information system that used the Big Bang and Use Case Points method, in this study the Agile method with Scrum Framework will be implemented based on considerations. Scrum as a framework that implements Sprints to break down complexity and accommodate priority features that need to be built from an information system, also divides the roles in implementing development into Product Owner, Developer Team and Scrum Master. The results of implementing this method can be a solution to several problems that arise during development, that is : dividing roles with existing teams, accepting all updates and changes originating from user evaluations through mutual agreement, work transparency which can be a reference in assigning the workload of each team members, regular periodic inspections to remind each member of development targets and goals, as well as adapt to implementing conditions, especially in adjusting communication and implementation times. So make information system development time can implemented shorter.

Scrum Framework Implementation for Building an Application of Monitoring and Booking E-Bus Based on QRCode

ABSTRACTThe increasing public interest in using the public transportation will reduce the volume of vehicles operating on the streets. The derivative of the description above is how to make people prefer to use bus transportation instead of using private vehicles in traveling within the city. Currently, there is 192.5 million smartphone’s user, in the other hand, the Indonesia government also supported the public transportation such as electrical bus. In November 2022, at KTT G20 Bali, INKA (Indonesia State-Owned Enterprise) and an academic institution consortium released 30 units of electrical buses. From that problem and opportunity, this research aims to propose an application that provides comprehensive information on public transportation, especially inner-city buses. So that, the user could easily track and book the bus. The proposed application is a real-time web-based application aimed at the public as users. This application is accessed using electronic devices such as cell phones, tablets, laptops, and computers. In this research we also proposed conceptual and scrum method for further implementation. We used the Scrum method to build the proposed application, the roles of the scrum team are one product owner, one scrum master, two development teams (UI/UX and developer), and 2 sprints. Implementing the Scrum method in the development process could help organize and increase team productivity. The result of this research is the prototype of a Monitoring and Booking e-Bus Based on a QR Code. In future research we would like to implement this concept and survey the user experience with PIECES framework to get the user comfort in using the proposed application.

Critical incidence reporting about medical teaching.

Previous end-of-semester evaluation cycles at our medical school revealed critical incidents about medical teaching. In one instance, a lecturer had frightened students, and in another case, a learning video contained misogynist statements. However, incident information reached the office of the dean too late for appropriate measures. Critical teaching incidents can compromise students and lecturers personally and may adversely affect the medical training. Early identification and efficient resolution are required to protect personal integrity and wellbeing of all parties, to ensure teaching quality and to prevent future incidents. Although critical incident reporting systems (CIRS) are well established in healthcare systems to prevent patient harm, a personal approach of complained management is still common in the field of teaching. However, due to the large number of students and the broad range of issues that could arise, an appropriate processing appears not to be warranted. Emotional thresholds and confidentiality requirements may prevent students and lecturers to address complaints and concerns. Parties may fear social pressure, disadvantages in their studies or work, and reprisal. We set up a CIRS which was made available to students and lecturers after only 2 months of development and roll out of the associated IT project. To this end, we used an agile project management methodology based on the Scrum framework because of its simplicity, its potential of adaption and its ability to enhance team productivity.1 Development started with definition of needs regarding the CIRS, the so-called ‘product backlog’ by the ‘product owner’ represented by the Dean for medical education. Only minimum requirements of functionality were claimed for the time of launch. Subsequently, the ‘Scrum master’, in person the head of eHealth applications, called a meeting with the development team to prioritise activities and divide the project into ‘sprint cycles’ that should be completed within a two-month time-box. The development team consisted of the division head of student- and lecturer administration, the division head of quality development in medical education, and the university hospital healthcare risk manager. During the following Scrum process, frequent brief meetings were held to adjust prioritisation of tasks according to upcoming challenges and impediments and to functionalities achieved so far. CIRS for teaching was launched in due time. The CIRS application works on the learning management system of our medical school. Access is available for enrolled students and lecturers of the respective courses. Anonymity of submitters is ensured unless they agree to their identities being revealed. Incidences were categorised within a pre-defined drop-down menu. Categories included unacceptable behaviours of lecturers or students, no-show of the lecturer, poor teaching quality, irregularities during the exam, irregularities about allocation of resources, problems concerning use of digital teaching media, technical and organisational problems to enrol at the university hospital, no availability or cleanliness of course rooms, and miscellaneous. In addition, submitters can enter free text commentaries into a dialogue box. Each input will be sent immediately and directly to the responsible body and may be forwarded to the Dean for medical education depending on importance.