Supporting the Transition to an Agile Test Matrix

Korošec, Robert; Pfarrhofer, Roman

doi:10.1109/icst.2015.7102632

Cited by 3 publications

(2 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Agile has brought the concept of the time-boxed development, where sprints are managing the development process within a short time and a limited scope. Agile also adopted the cutting edge process such as continuous integration, where the developer checks-in the code several times a day and at the same time it is recompiled [2]. It shows that software is continuously changing.…”

Section: • Comprehension Of the Requirementsmentioning

confidence: 99%

Introduction to Lean Canvas Transformation Models and Metrics in Software Testing

Nidagundi¹,

Novickis

2016

Applied Computer Systems

View full text Add to dashboard Cite

Software plays a key role nowadays in all fields, from simple up to cutting-edge technologies and most of technology devices now work on software. Software development verification and validation have become very important to produce the high quality software according to business stakeholder requirements. Different software development methodologies have given a new dimension for software testing. In traditional waterfall software development software testing has approached the end point and begins with resource planning, a test plan is designed and test criteria are defined for acceptance testing. In this process most of test plan is well documented and it leads towards the time-consuming processes. For the modern software development methodology such as agile where long test processes and documentations are not followed strictly due to small iteration of software development and testing, lean canvas transformation models can be a solution. This paper provides a new dimension to find out the possibilities of adopting the lean transformation models and metrics in the software test plan to simplify the test process for further use of these test metrics on canvas.

show abstract

Section: • Comprehension Of the Requirementsmentioning

confidence: 99%

Introduction to Lean Canvas Transformation Models and Metrics in Software Testing

Nidagundi¹,

Novickis

2016

Applied Computer Systems

View full text Add to dashboard Cite

show abstract

“…However, this additional development time has to be contrasted with potential extra time spent fixing the code at a later stage based on reported defects. Korosec and Pfarrhofer [15] reported the transition towards an agile software development, which saw the transformation of their test suite from mostly automated system to unit tests. In-fact, system tests provide the best protection against software defects, however, they come with a high maintenance cost as described by Korosec and Pfarrhofer.…”

mentioning

confidence: 99%

A practical guide towards agile test-driven development for scientific software projects

Teschner

2020

Preprint

View full text Add to dashboard Cite

Software testing has received much attention over the last years and has reached such critical importance that agile software development practices put software testing at its core. Agile software development is successfully applied in large-scale industrial software developments but due to its granular responsibilities with roles assigned to various members of the development team, these practices may not be applicable to scientific code development, especially in an academic environment, where it is not uncommon that the codebase is developed, maintained and used by a single person. Even for collaborative scientific software development, financed through external grants, the end-users are typically still part of the development team. This is in contrast to how software is developed in many industries, where the development team and end-users are two separate entities. There are, however, many good code development practices that can be adopted for scientific software projects. Specifically, the intention of this article is to take the centrepiece of agile software development -the test-driven development -and tailor it to scientific and academic, single-user code development. In this study, a c++ starter project is developed and made available, based on the meson build system, which provides native support for software testing. It is used to show how a simple linear algebra application, found in many scientific and academic applications, can be developed and how simple unit, integration and system tests can be created that are managed through the meson build system. In this way, we are able to minimise software defects and reduce the risk to interpret incorrect data generated by erroneous software that may result, in the worst case, in the wrong conclusions to be drawn. Each layer of testing presents one additional layer of protection against such software defects and we will explore how these may be incorporated with minimum overhead to produce bug-free software.

show abstract

SAFe transformation in a large financial corporation

Putta,

Paasivaara,

Lassenius

2023

Empir Software Eng

View full text Add to dashboard Cite

As agile software development is increasingly adopted in the software industry, the popularity of scaling frameworks supporting adoption in large development contexts is increasing rapidly. While several such frameworks exist, the most popular one at the moment is the Scaled Agile Framework (SAFe). Despite its popularity, there exists limited research on its usage and adoption. In this paper, we contribute by presenting a single case study in a large financial organization, studying the transformation reasons, transformation process, as well as the benefits, and challenges of SAFe adoption. We conducted 24 semi-structured interviews with 27 interviewees and analyzed the transcribed interviews using open and axial coding. We identified 17 reasons for SAFe adoption in this organization, of which the most salient ones were to shorten the time to market, improve collaboration, and use a well-described and comprehensive framework. An industry context-specific reason was the popularity of SAFe in the financial sector. The transformation in the case organization was top-down and proceeded step-wise. The most significant activities during the transformation were piloting, education, coaching, and the forming of agile release trains. Our case also implemented "Scrum tours" to increase the understanding of lean and agile principles. We identified 13 benefits of SAFe, of which improved collaboration, transparency, and shorter time to market were considered the most important. We identified a total of 16 challenges, with the most salient one being aligning the release trains with value streams. Failing with this led to cross-release train dependencies and coordination overhead, inhibiting agility. Further, the organization did not get rid of projects and project managers, which led to priority clashes and coordination overhead.

show abstract

Supporting the Transition to an Agile Test Matrix

Cited by 3 publications

References 1 publication

Introduction to Lean Canvas Transformation Models and Metrics in Software Testing

Introduction to Lean Canvas Transformation Models and Metrics in Software Testing

A practical guide towards agile test-driven development for scientific software projects

SAFe transformation in a large financial corporation

Contact Info

Product

Resources

About