| 1. |
- Berntsson Svensson, Richard, 1978, et al.
(författare)
-
The unfulfilled potential of data-driven decision making in agile software development
- 2019
-
Ingår i: Lecture Notes in Business Information Processing. - Cham : Springer International Publishing. - 1865-1356 .- 1865-1348. - 9783030190330 ; 355, s. 69-85
-
Konferensbidrag (refereegranskat)abstract
- With the general trend towards data-driven decision making (DDDM), organizations are looking for ways to use DDDM to improve their decisions. However, few studies have looked into the practitioners view of DDDM, in particular for agile organizations. In this paper we investigated the experiences of using DDDM, and how data can improve decision making. An emailed questionnaire was sent out to 124 industry practitioners in agile software developing companies, of which 84 answered. The results show that few practitioners indicated a wide-spread use of DDDM in their current decision making practices. The practitioners were more positive to its future use for higher-level and more general decision making, fairly positive to its use for requirements elicitation and prioritization decisions, while being less positive to its future use at the team level. The practitioners do see a lot of potential for DDDM in an agile context; however, currently unfulfilled.
|
|
| 2. |
- Alahyari, Hiva, 1979, et al.
(författare)
-
A study of value in agile software development organizations
- 2017
-
Ingår i: Journal of Systems and Software. - : Elsevier BV. - 0164-1212 .- 1873-1228. ; 125, s. 271-288
-
Tidskriftsartikel (refereegranskat)abstract
- The Agile manifesto focuses on the delivery of valuable software. In Lean, the principles emphasise value, where every activity that does not add value is seen as waste. Despite the strong focus on value, and that the primary critical success factor for software intensive product development lies in the value domain, no empirical study has investigated specifically what value is. This paper presents an empirical study that investigates how value is interpreted and prioritised, and how value is assured and measured. Data was collected through semi-structured interviews with 23 participants from 14 agile software development organisations. The contribution of this study is fourfold. First, it examines how value is perceived amongst agile software development organisations. Second, it compares the perceptions and priorities of the perceived values by domains and roles. Third, it includes an examination of what practices are used to achieve value in industry, and what hinders the achievement of value. Fourth, it characterises what measurements are used to assure, and evaluate value-creation activities. (C) 2016 Elsevier Inc. All rights reserved.
|
|
| 3. |
- Alahyari, Hiva, 1979, et al.
(författare)
-
An exploratory study of waste in software development organizations using agile or lean approaches : A multiple case study at 14 organizations
- 2019
-
Ingår i: Information and Software Technology. - : Elsevier B.V.. - 0950-5849 .- 1873-6025. ; 107, s. 78-94
-
Tidskriftsartikel (refereegranskat)abstract
- Context: The principal focus of lean is the identification and elimination of waste from the process with respect to maximizing customer value. Similarly, the purpose of agile is to maximize customer value and minimize unnecessary work and time delays. In both cases the concept of waste is important. Through an empirical study, we explore how waste is approached in agile software development organizations. Objective: This paper explores the concept of waste in agile/lean software development organizations and how it is defined, used, prioritized, reduced, or eliminated in practice Method: The data were collected using semi-structured open-interviews. 23 practitioners from 14 embedded software development organizations were interviewed representing two core roles in each organization. Results: Various wastes, categorized in 10 different categories, were identified by the respondents. From the mentioned wastes, not all were necessarily waste per se but could be symptoms caused by wastes. From the seven wastes of lean, Task-switching was ranked as the most important, and Extra-features, as the least important wastes according to the respondents’ opinion. However, most companies do not have their own or use an established definition of waste, more importantly, very few actively identify or try to eliminate waste in their organizations beyond local initiatives on project level. Conclusion: In order to identify, recognize and eliminate waste, a common understanding, and a joint and holistic view of the concept is needed. It is also important to optimize the whole organization and the whole product, as waste on one level can be important on another, thus sub-optimization should be avoided. Furthermore, to achieve a sustainable and effective waste handling, both the short-term and the long-term perspectives need to be considered. © 2018 Elsevier B.V.
|
|
| 4. |
- Ameller, D., et al.
(författare)
-
Handling Non-functional Requirements in Model-Driven Development: An Ongoing Industrial Survey
- 2015
-
Ingår i: 2015 IEEE 23rd International Requirements Engineering Conference (Re). - : IEEE. - 9781467369053
-
Konferensbidrag (refereegranskat)abstract
- Model-Driven Development (MDD) is no longer a novel development paradigm. It has become mature from a research perspective and recent studies show its adoption in industry. Still, some issues remain a challenge. Among them, we are interested in the treatment of non-functional requirements (NFRs) in MDD processes. Very few MDD approaches have been reported to deal with NFRs (and they do it in a limited way). However, it is clear that NFRs need to be considered somehow in the final product of the MDD process. To better understand how NFRs are integrated into the existing MDD approaches, we have initiated the NFR4MDD project, a multi-national empirical study, based on interviews with companies working on MDD projects. Our project aims at surveying the state of the practice for this topic. In this paper, we summarize our research protocol and present the current status of our study. The discussion will focus on the peculiarities of our study's context and organization involving about 20 researchers from 8 European countries.
|
|
| 5. |
- Berntsson Svensson, Richard, 1978, et al.
(författare)
-
A Case Study Evaluation of the Guideline-Supported QUPER Model for Elicitation of Quality Requirements
- 2015
-
Ingår i: Requirements Engineering: Foundation for Software Quality. - Cham : Springer-Verlag Berlin. - 0302-9743 .- 1611-3349. - 9783319161013 - 9783319161006 ; 9013, s. 230-246
-
Konferensbidrag (refereegranskat)abstract
- For market-driven software product developing organizations operating on a competitive open market, it is important to plan the product's releases so that they can reach the market as early as possible with a competitive level of quality compared to its competitors' products. Hence, quality requirements can be seen as a key competitive advantage. The QUPER model was developed with the aim to support high-level decision-making in release planning of quality requirements. As a follow up on previous studies on QUPER, this study investigates: What are practitioners' views on the utilities of QUPER extended with guidelines including domain-specific examples? [Principal ideas/results] In the presented case study, a set of detailed guidelines of how to apply QUPER in practice, including how to handle cost dependencies between quality requirements, was evaluated at a case company in the mobile handset domain with 24 professionals using real quality requirements. The results point to the importance of having concrete guidelines combined with instructive examples from real practice, while it is not always obvious for a practitioner to transfer cost-dependency examples into the domains that are different from the example domain. The transferability of guidelines and examples to support methodology adoption is an interesting issue for further research.
|
|
| 6. |
- Berntsson Svensson, Richard, 1978, et al.
(författare)
-
Aligning Quality Requirements and Test Results with QUPER's Roadmap View for Improved High-Level Decision-Making
- 2015
-
Ingår i: 2015 Ieee/Acm 2nd International Workshop on Requirements Engineering and Testing (Ret). - : IEEE. - 9781479919345
-
Konferensbidrag (refereegranskat)abstract
- Weak alignment of requirements engineering (RE) and Software Testing (ST) may lead to problems in delivering the required products in time with the right quality. Despite the importance of aligning RE and ST, the research have mainly been focused on one or the other of RE and ST. Previous work has identified several challenges in aligning RE and ST related to Quality Requirements, for example, the need for tool support for QR, defining and managing QR, and verification of QR. In this position paper, we introduce a new view of the QUPER model, namely aligning QR targets and test results in QUPERs roadmap view. The alignment view was evaluated at a case company with 13 practitioners. The results show that the alignment of QR and test results using QUPER's roadmap view was viewed as an important input to the decision-making process.
|
|
| 7. |
- Berntsson Svensson, Richard, 1978-, et al.
(författare)
-
BAM : backlog assessment method
- 2019
-
Ingår i: Lecture Notes in Business Information Processing. - Cham : Springer Verlag. - 1865-1348. - 9783030190330 ; , s. 53-68
-
Konferensbidrag (refereegranskat)abstract
- The necessity of software as stand-alone products, and as central parts of non-traditional software products have changed how software products are developed. It started with the introduction of the agile manifesto and has resulted in a change of how software process improvements (SPI) are conducted. Although there are agile SPI methods and several agile practices for evaluating and improving current processes and ways-of-working, no method or practices for evaluating the backlog exists. To address this gap, the Backlog Assessment Method (BAM) was developed and applied in collaboration with Telenor Sweden. BAM enables agile organizations to assess backlogs, and assure that the backlog items are good-enough for their needs and well aligned with the decision process. The results from the validation show that BAM is feasible and relevant in an industrial environment, and it indicates that BAM is useful as a tool to perform analysis of items in a specific backlog. © The Author(s) 2019.
|
|
| 8. |
- Berntsson Svensson, Richard, 1978, et al.
(författare)
-
Creativity Techniques for More Creative Requirements: Theory vs. Practice
- 2015
-
Ingår i: EUROMICRO Conference on Software Engineering and Advanced Applications (SEAA 2015), August 26-28. - : IEEE. - 9781467375856
-
Konferensbidrag (refereegranskat)abstract
- Requirements engineering was initially regarded as a front-end activity to form a basis for the coming activities of software development, which can be achieved by gathering and producing unambiguous and consistent requirements. However, in recent years, requirements engineering has been recognized as a creative process. A systematic literature review followed by an online questionnaire with practitioners were employed to identify a comprehensive overview of existing empirical evidence using creativity techniques in the requirements engineering process. The results show a limited range of applied creativity techniques with insufficient empirical evidence to adequately evaluate if the techniques create more creative requirements. The contribution of this study is threefold: First, it compares which creativity techniques have been empirically evaluated in literature. Second, it compares the identified creativity techniques. Third, it includes an examination of which creativity techniques are used in industry.
|
|
| 9. |
- Berntsson Svensson, Richard, 1978, et al.
(författare)
-
Is role playing in Requirements Engineering Education increasing learning outcome?
- 2017
-
Ingår i: Requirements Engineering. - : Springer Science and Business Media LLC. - 0947-3602 .- 1432-010X. ; 22:4, s. 475-489
-
Tidskriftsartikel (refereegranskat)abstract
- Requirements Engineering has attracted a great deal of attention from researchers and practitioners in recent years. This increasing interest requires academia to provide students with a solid foundation in the subject matter. In Requirements Engineering Education (REE), it is important to cover three fundamental topics: traditional analysis and modeling skills, interviewing skills for requirements elicitation, and writing skills for specifying requirements. REE papers report about using role playing as a pedagogical tool; however, there is a surprising lack of empirical evidence on its utility. In this paper we investigate whether a higher grade in a role playing project have an effect on students' score in an individual written exam in a Requirements Engineering course. Data are collected from 412 students between the years of 2007 and 2014 at Lund University and Chalmers | University of Gothenburg. The results show that students who received a higher grade in the role playing project scored statistically significant higher in the written exam compared to the students with a lower role playing project grade.
|
|
| 10. |
- Berntsson Svensson, Richard, 1978
(författare)
-
Measuring team innovativeness: A multiple case study of agile and lean software developing companies
- 2017
-
Ingår i: Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics). - Cham : Springer International Publishing. - 1611-3349 .- 0302-9743. ; 10611 LNCS, s. 37-51
-
Konferensbidrag (refereegranskat)abstract
- [Context/Background] Innovation is seen as the basis of competitive economy and measuring the innovation process is important fo r organizations. In the literature, focus has been on innovation and innovation capabilities on an organizational level, while few studies has been placed on innovation at team level. Furthermore, organizations tend to focus on the measurement of innovation to input and outputs of the innovation process and ignoring the process in-between. [Goal] This paper explores how a team’s innovation capability is measured, and can be measured in practice in agile and lean software developing companies. [Method] It is based on data collected through semi-structured interviews with 28 practitioners from 11 software developing companies. [Results] The contribution of this study is twofold: First, it characterizes which metrics are used in industry to measure a team’s innovation capability. Second, it identifies which metrics that could be used in practice to measure a team’s innovation capability. [Conclusions] Measuring the performance of the innovation process is not seen as important during product planning and development.
|
|
