Comparison of Scrum Maturity Between Internal and External Software Development: A Case Study at One of the State-Owned Banks in Indonesia

Zelfia, Hidayatul; Simanungkalit, Tiarma; Raharjo, Teguh

doi:10.1109/icisit54091.2022.9872843

Cited by 4 publications

(8 citation statements)

References 17 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Methodologies are free to specify how to execute the stages and technical processes that the ISO/IEC/IEEE standards propose, their execution order, and even select which processes will be executed [ 67 ]. However, presumably, at least the following processes must be present in the lifecycle: (1) planning and requirements gathering, (2) solution analysis, (3) solution design, (4) solution coding and unit testing (construction), (5) integration and testing (implementation), and (6) operation and maintenance [ 64 , 90 , 91 , 92 ]. Additionally, all the work done in each of the activities carried out should be well documented.…”

Section: Methodologies Designed For the Development Of Iotssmentioning

confidence: 99%

“…These methodologies split the system to be developed into deliverable products, which in turn are organised into tasks that last from 2 to 4 weeks (called sprint in Scrum) [ 92 , 93 ]. This way of organising the work contrasts with other development methodologies, such as Waterfall, Spiral, RP, etc., that take the problem to be solved in its entirety.…”

Section: Methodologies Designed For the Development Of Iotssmentioning

confidence: 99%

“…The order in which they are executed may be different, depending on the design of the methodology. For example, tests in Scrum are performed at the end [ 92 ], while in XP they are written at the beginning of the development cycle, as stipulated by TDD (Test-Driven Development) [ 97 ].…”

Section: Methodologies Designed For the Development Of Iotssmentioning

confidence: 99%

“…For agile methodologies, ISO/IEC/IEEE 26515:2018 defines user stories, scenarios, and characters as tools for obtaining and analysing requirements, while use cases are proposed as a design technique [ 99 ]. For example, Scrum proposes to use user stories as a tool for acquiring requirements [ 7 , 8 , 92 , 100 ]. User stories are simple narratives that illustrate a user requirement from the perspective of a person or actor [ 98 ].…”

Section: Methodologies Designed For the Development Of Iotssmentioning

confidence: 99%

See 3 more Smart Citations

Agile Methodologies Applied to the Development of Internet of Things (IoT)-Based Systems: A Review

Guerrero-Ulloa

Rodríguez-Domínguez

Hornos

2023

Sensors

View full text Add to dashboard Cite

Throughout the evolution of software systems, empirical methodologies have been used in their development process, even in the Internet of Things (IoT) paradigm, to develop IoT-based systems (IoTS). In this paper, we review the fundamentals included in the manifesto for agile software development, especially in the Scrum methodology, to determine its use and role in IoTS development. Initially, 4303 documents were retrieved, a number that was reduced to 186 after applying automatic filters and by the relevance of their titles. After analysing their contents, only 60 documents were considered. Of these, 38 documents present the development of an IoTS using some methodology, 8 present methodologies focused on the construction of IoTS software, and 14 present methodologies close to the systems life cycle (SLC). Finally, only one methodology can be considered SLC-compliant. Out of 38 papers presenting the development of some IoTS following a methodology for traditional information systems (ISs), 42.1% have used Scrum as the only methodology, while 10.5% have used Scrum combined with other methodologies, such as eXtreme Programming (XP), Kanban and Rapid Prototyping. In the analysis presented herein, the existing methodologies for developing IoTSs have been grouped according to the different approaches on which they are based, such as agile, modelling, and service oriented. This study also analyses whether the different proposals consider the standard stages of the development process or not: planning and requirements gathering, solution analysis, solution design, solution coding and unit testing (construction), integration and testing (implementation), and operation and maintenance. In addition, we include a review of the automated frameworks, platforms, and tools used in the methodologies analysed to improve the development of IoTSs and the design of their underlying architectures. To conclude, the main contribution of this work is a review for IoTS researchers and developers regarding existing methodologies, frameworks, platforms, tools, and guidelines for the development of IoTSs, with a deep analysis framed within international standards dictated for this purpose.

show abstract

Section: Methodologies Designed For the Development Of Iotssmentioning

confidence: 99%

Section: Methodologies Designed For the Development Of Iotssmentioning

confidence: 99%

Section: Methodologies Designed For the Development Of Iotssmentioning

confidence: 99%

Section: Methodologies Designed For the Development Of Iotssmentioning

confidence: 99%

See 2 more Smart Citations

Agile Methodologies Applied to the Development of Internet of Things (IoT)-Based Systems: A Review

Guerrero-Ulloa

Rodríguez-Domínguez

Hornos

2023

Sensors

View full text Add to dashboard Cite

show abstract

“…Panjaitan et al [14] discussed the results and the recommendations in a thorough approach. In addition, Scrum maturity level can also be compared between two groups as conducted in research [16] and [17]. Setiyawan et al [16] compared Scrum practices in a Corporate Strategy group and an Information Technology (IT) group at a telecommunication company, whereas Zelfia et al [17] compared an IT group and a temporary unit at a state-owned bank.…”

Section: Introductionmentioning

confidence: 99%

Comparing Scrum Maturity of Digital and Business Process Reengineering Groups: A Case Study at an Indonesia’s State-Owned Bank

Patara,

Raharjo

2023

IJACSA

View full text Add to dashboard Cite

Bank XYZ, an Indonesia's state-owned bank, has been conducting business and digital transformation throughout its organization. Based on a recent McKinsey survey, less than 30% of organizations succeed in transformation. Fast changing business requirements and various technology-based initiatives enforce the organization to employ an Agile methodology and Scrum, to cope with the situation. Group Grp-DGT and Grp-BPR are two groups in Bank XYZ that manage their projects using Scrum. Grp-DGT develops digital projects, whereas Grp-BPR develops Business Process Reengineering (BPR) projects. Scrum maturity in both groups needs to be appraised to promote sustainability in the long run. Comparing Scrum maturity between digital and BPR projects has not been done in the previous works, especially in a state-owned bank in Indonesia. This research will help the organization through the research output which are Scrum maturity level at both groups and proposed recommendations to improve Scrum practices. The other organizations can benefit from the recommendations as well. Scrum maturity model (SMM) is used to appraise the practices, while Agile Maturity (AMM) is used to calculate the maturity rating. From this research, it is found that Grp-DGT has reached maturity level 5 (optimizing), whereas Grp-BPR is still at level 1 (initial). Based on assessment results and Scrum guides, the recommendations are then drafted. There are 15 recommendations proposed to Grp-BPR to reach level 2 and onwards.

show abstract

Impact of the Kanban Maturity Model on a Team’s Agile Transformation: Tripling Throughput and Elevating Quality in Three Months

Trzesicki,

Marek,

Przybylek

2024

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

Agile transformations have been a significant challenge since the beginning of the agile movement, with numerous researchers and practitioners suggesting various structured approaches and guidelines. The Kanban Maturity Model (KMM) is a relatively new approach that focuses on assessing the current maturity level of an organisation, with an emphasis on a spectrum of Kanban practices. This paper presents the initial results of applying the KMM as a guide for subsequent steps in Kanban implementation and agile transformation. The exploratory case study describes the application of the KMM in the agile transformation of a software development team within a midsize organisation. Despite previous unsuccessful attempts to implement Scrum, the adoption of KMM facilitated a rapid and successful implementation of the Kanban Method. Within three months, the team’s throughput tripled, and the quality of the developed software improved significantly. The results suggest that the KMM can be successfully used as an effective guideline for agile transformation of software development teams.

show abstract

Comparison of Scrum Maturity Between Internal and External Software Development: A Case Study at One of the State-Owned Banks in Indonesia

Cited by 4 publications

References 17 publications

Agile Methodologies Applied to the Development of Internet of Things (IoT)-Based Systems: A Review

Agile Methodologies Applied to the Development of Internet of Things (IoT)-Based Systems: A Review

Comparing Scrum Maturity of Digital and Business Process Reengineering Groups: A Case Study at an Indonesia’s State-Owned Bank

Impact of the Kanban Maturity Model on a Team’s Agile Transformation: Tripling Throughput and Elevating Quality in Three Months

Contact Info

Product

Resources

About