SwePub - sökning: WFRF:(Berntsson Svensson Richa...

Numrering	Referens	Omslagsbild	Hitta
1.	Berntsson Svensson, Richard, 1978, et al. (författare) Not all requirements prioritization criteria are equal at all times: A quantitative analysis 2024 Ingår i: Journal of Systems and Software. - 0164-1212. ; 209 Tidskriftsartikel (refereegranskat)abstract Requirement prioritization is recognized as an important decision-making activity in requirements engineering. Requirement prioritization is applied to determine which requirements should be implemented and released. In order to prioritize requirements, there are several approaches/techniques/tools that use different requirements prioritization criteria, which are often identified by gut feeling instead of an in-depth analysis of which criteria are most important to use. Therefore, in this study we investigate which requirements prioritization criteria are most important to use in industry when determining which requirements are implemented and released, and if the importance of the criteria change depending on how far a requirement has reached in the development process. We conducted a quantitative study where quantitative data was collected through a case study of one completed project from one software developing company by extracting 32,139 requirements prioritization decisions based on eight requirements prioritization criteria for 11,110 requirements. The results show that not all requirements prioritization criteria are equally important, and this change depending on how far a requirement has reached in the development process. For example, for requirements prioritization decisions before iteration/sprint planning, having high Business value had an impact on the decisions, but after iteration/sprint planning, having high Business value had no impact. Editor's note: Open Science material was validated by the Journal of Systems and Software Open Science Board.
2.	Berntsson Svensson, Richard, 1978, et al. (författare) Quality Requirements in Industrial Practice - An Extended Interview Study at Eleven Companies 2011 Ingår i: IEEE Transactions on Software Engineering. - 0098-5589 .- 1939-3520. Tidskriftsartikel (refereegranskat)abstract In order to create a successful software product and assure its quality, it is not enough to fulfill the functional requirements, it is also crucial to find the right balance among competing quality requirements (QR). An extended, previously piloted, interview study was performed to identify specific challenges associated with the selection, trade-off, and management of QR in industrial practice. Data was collected through semi-structured interviews with eleven product managers and eleven project leaders from eleven software companies. The contribution of this study is fourfold: First, it compares how QR are handled in two cases, companies working in business-to-business markets, and companies that are working in business-to-consumer markets. These two are also compared in terms of impact on the handling of QRs. Second, it compares the perceptions and priorities of QR by product and project management respectively. Third, it includes an examination of the interdependencies among quality requirements perceived as most important by the practitioners. Fourth, it characterizes the selection and management of QR in down-stream development activities.
3.	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.
4.	Gad, Helge, et al. (författare) MTH1 inhibition eradicates cancer by preventing sanitation of the dNTP pool 2014 Ingår i: Nature. - : Nature Publishing Group. - 0028-0836 .- 1476-4687. ; 508:7495, s. 215-221 Tidskriftsartikel (refereegranskat)abstract Cancers have dysfunctional redox regulation resulting in reactive oxygen species production, damaging both DNA and free dNTPs. The MTH1 protein sanitizes oxidized dNTP pools to prevent incorporation of damaged bases during DNA replication. Although MTH1 is non-essential in normal cells, we show that cancer cells require MTH1 activity to avoid incorporation of oxidized dNTPs, resulting in DNA damage and cell death. We validate MTH1 as an anticancer target in vivo and describe small molecules TH287 and TH588 as first-in-class nudix hydrolase family inhibitors that potently and selectively engage and inhibit the MTH1 protein in cells. Protein co-crystal structures demonstrate that the inhibitors bindin the active site of MTH1. The inhibitors cause incorporation of oxidized dNTPs in cancer cells, leading to DNA damage, cytotoxicity and therapeutic responses in patient-derived mouse xenografts. This study exemplifies the non-oncogene addiction concept for anticancer treatment and validates MTH1 as being cancer phenotypic lethal.
5.	Agren, P., et al. (författare) Agile software development one year into the COVID-19 pandemic 2022 Ingår i: Empirical Software Engineering. - : Springer Science and Business Media LLC. - 1382-3256 .- 1573-7616. ; 27:6 Tidskriftsartikel (refereegranskat)abstract As a result of the COVID-19 pandemic, many agile practitioners had to transition into a remote work environment. Despite remote work not being a new concept for agile software practitioners, the forced or recommended nature of remote work is new. This study investigates how the involuntary shift to remote work and how social restrictions imposed by the COVID-19 pandemic have affected agile software development (ASD), and how agile practitioners have been affected in terms of ways of working. An explanatory sequential mixed methods study was performed. Data were collected one year into the COVID-19 pandemic through a questionnaire with 96 respondents and in-depth semi-structured interviews with seven practitioners from seven different companies. Data were analyzed through Bayesian analysis and thematic analysis. The results show, in general, that the aspects of ASD that have been the most affected is communication and social interactions, while technical work aspects have not experienced the same changes. Moreover, feeling forced to work remotely has a significant impact on different aspects of ASD, e.g., productivity and communication, and industry practitioners' employment of agile development and ways of working have primarily been affected by the lack of social interaction and the shift to digital communication. The results also suggest that there may be a group maturing debt when teams do go back into office, as digital communication and the lack of psychological safety stand in the way for practitioners' ability to have sensitive discussions and progress as a team in a remote setting.
6.	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.
7.	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.
8.	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.
9.	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.
10.	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.
11.	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.
12.	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.
13.	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.
14.	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.
15.	Berntsson Svensson, Richard, 1978-, et al. (författare) Selecting creativity techniques for creative requirements: An evaluation of four techniques using creativity workshops 2015 Ingår i: 23rd IEEE International Requirements Engineering Conference, RE 2015, Ottawa, Canada, 24-28 August. - : IEEE. - 9781467369053 ; , s. 66-75 Konferensbidrag (refereegranskat)abstract Requirements engineering is recognized as a creative process where stakeholders jointly discover new creative ideas for innovative and novel products that eventually are expressed as requirements. This paper evaluates four different creativity techniques, namely Hall of Fame, Constraint Removal, Brainstorming, and Idea Box, using creativity workshops with students and industry practitioners. In total, 34 creativity workshops were conducted with 90 students from two universities, and 86 industrial practitioners from six companies. The results from this study indicate that Brainstorming can generate by far the most ideas, while Hall of Fame generates most creative ideas. Idea Box generates the least number of ideas, and the least number of creative ideas. Finally, Hall of Fame was the technique that led to the most number of requirements that was included in future releases of the products. © 2015 IEEE.
16.	Berntsson Svensson, Richard, 1978, et al. (författare) Toward Becoming a Data-Driven Organization: Challenges and Benefits 2020 Ingår i: 14th International Conference on Research Challenges in Information Science. - Cham : Springer. Konferensbidrag (refereegranskat)
17.	Bjarnason, Elizabeth, et al. (författare) Reflecting on Evidence-Based Timelines 2014 Ingår i: IEEE Software. - 0740-7459 .- 1937-4194. ; 31:4, s. 37-43 Tidskriftsartikel (refereegranskat)abstract Project retrospectives can be powerful tools for project teams to collectively identify communication gaps and practices to improve for future projects. However, even if project members take the time for a retrospective, it can be hard to correctly remember and jointly discuss past events in a constructive way. Fact-based timelines that visualize a project's events offer a possible solution.
18.	Claps, Gerry, et al. (författare) On the journey to continuous deployment: technical and social challenges along the way 2015 Ingår i: Information and Software Technology. - : Elsevier BV. - 0950-5849. ; 57:1, s. 21-31 Tidskriftsartikel (refereegranskat)abstract Continuous deployment (CD) is an emerging software development process with organisations such as Facebook, Microsoft, and IBM successfully implementing and using the process. The CD process aims to immediately deploy software to customers as soon as new code is developed, and can result in a number of benefits for organizations, such as: new business opportunities, reduced risk for each release, and prevent development of wasted software. There is little academic literature on the challenges organisations face when adopting the CD process, however there are many anecdotal challenges that organisations have voiced on their online blogs. The aim of this research is to examine the challenges faced by organisations when adopting CD as well as the strategies to mitigate these challenges. An explorative case study technique that involves in-depth interviews with software practitioners in an organisation that has adopted CD was conducted to identify these challenges. This study found a total of 20 technical and social adoption challenges that organisations may face when adopting the CD process. The results are discussed to gain a deeper understanding of the strategies employed by organisations to mitigate the impacts of these challenges. While a number of individual technical and social adoption challenges were uncovered by the case study in this research, most challenges were not faced in isolation. The severity of these challenges were reduced by a number of mitigation strategies employed by the case study organization. It is concluded that organisations need to be well prepared to handle technical and social adoption challenges with their existing expertise, processes and tools before adopting the CD process. For practitioners, knowing how to address the challenges an organization may face when adopting the CD process provides a level of awareness that they previously may not have had.
19.	Daneva, M., et al. (författare) Welcome from the workshop chairs 2014 Ingår i: 2014 IEEE 4th International Workshop on Empirical Requirements Engineering, EmpiRE 2014 - Proceedings. - 9781479963379 Konferensbidrag (övrigt vetenskapligt/konstnärligt)
20.	Debbiche, Adam, et al. (författare) Challenges When Adopting Continuous Integration: A Case Study 2014 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. - 9783319138350 ; 8892, s. 17-32 Tidskriftsartikel (refereegranskat)abstract The complexity of software development has increased over the last few years. Customers today demand higher quality and more stable software with shorter delivery time. Software companies strive to improve their processes in order to meet theses challenges. Agile practices have been widely praised for the focus they put on customer collaboration and shorter feedback loops. Companies that have well established agile practices have been trying to improve their processes further by adopting continuous integration - the concept where teams integrate their code several times a day. However, adopting continuous integration is not a trivial task. This paper presents a case study in which we, based on interviews at a major Swedish telecommunication services and equipment provider, assess the challenges of continuous integration. The study found 23 adoption challenges that organisations may face when adopting the continuous integration process.
21.	Fernandez, Stefania, 1986, et al. (författare) A Survey of Practitioners Use of Open Innovation 2017 Ingår i: 43rd Euromicro Conference on Software Engineering and Advanced Applications. - 9781538621417 Konferensbidrag (refereegranskat)abstract In recent years, the influence of open innovation has become more and more important in the development of software products and services. However, open innovation is still unexplored for software-intensive organizations and its potential impact on the organization's innovative performance. In this paper we present the results of an empirical study carried out to gauge common experiences within open innovation in the requirements engineering process, and to understand the barriers and drivers for using open innovation. A web-based questionnaire was sent out to 54 industry practitioners, of which 35 answered. The results show that open innovation as part of the requirements engineering process is becoming more and more fully exploited from both the outside and inside. Moreover, potential drivers for using open innovation include, new generated ideas and higher costumer benefits, while identified barriers include, hard finding the right partner and lack of innovativeness.
22.	Gomes, Francisco, 1987, et al. (författare) Evaluating the Effects of Different Requirements Representations on Writing Test Cases 2020 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. ; 12045 LNCS, s. 257-274 Konferensbidrag (refereegranskat)abstract Context and Motivation One must test a system to ensure that the requirements are met, thus, tests are often derived manually from requirements. However, requirements representations are diverse; from traditional IEEE-style text, to models, to agile user stories, the RE community of research and practice has explored various ways to capture requirements. Question/problem But, do these different representations influence the quality or coverage of test suites? The state-of-the-art does not provide insights on whether or not the representation of requirements has an impact on the coverage, quality, or size of the resulting test suite. Results In this paper, we report on a family of three experiment replications conducted with 148 students which examines the effect of different requirements representations on test creation. We find that, in general, the different requirements representations have no statistically significant impact on the number of derived tests, but specific affordances of the representation effect test quality, e.g., traditional textual requirements make it easier to derive less abstract tests, whereas goal models yield less inconsistent test purpose descriptions. Contribution Our findings give insights on the effects of requirements representation on test derivation for novice testers. Our work is limited in the use of students.
23.	Gren, Lucas, et al. (författare) Is it possible to disregard obsolete requirements? : An initial experiment on a potentially new bias in software effort estimation 2017 Ingår i: Proceedings - 2017 IEEE/ACM 10th International Workshop on Cooperative and Human Aspects of Software Engineering, CHASE 2017. - : Institute of Electrical and Electronics Engineers Inc.. - 9781538640395 ; , s. 56-61 Konferensbidrag (refereegranskat)abstract Effort estimation is a complex area in decision-making, and is influenced by a diversity of factors that could increase the estimation error. The effects on effort estimation accuracy of having obsolete requirements in specifications have not yet been studied. This study aims at filling that gap. A total of 150 students were asked to provide effort estimates for different amounts of requirements, and one group was explicitly told to disregard some of the given requirements. The results show that even the extra text instructing participants to exclude requirements in the estimation task, had the subjects give higher estimates. The effect of having obsolete requirements in requirements specifications and backlogs in software effort estimation is not taken into account enough today, and this study provides empirical evidence that it possibly should. We also suggest different psychological explanations to the found effect. © 2017 IEEE.
24.	Gren, Lucas, 1984-, et al. (författare) Is it possible to disregard obsolete requirements? a family of experiments in software effort estimation 2021 Ingår i: Requirements Engineering. - : Springer Science and Business Media Deutschland GmbH. - 0947-3602 .- 1432-010X. ; :3, s. 459-480 Tidskriftsartikel (refereegranskat)abstract Expert judgement is a common method for software effort estimations in practice today. Estimators are often shown extra obsolete requirements together with the real ones to be implemented. Only one previous study has been conducted on if such practices bias the estimations. We conducted six experiments with both students and practitioners to study, and quantify, the effects of obsolete requirements on software estimation. By conducting a family of six experiments using both students and practitioners as research subjects (N= 461), and by using a Bayesian Data Analysis approach, we investigated different aspects of this effect. We also argue for, and show an example of, how we by using a Bayesian approach can be more confident in our results and enable further studies with small sample sizes. We found that the presence of obsolete requirements triggered an overestimation in effort across all experiments. The effect, however, was smaller in a field setting compared to using students as subjects. Still, the over-estimations triggered by the obsolete requirements were systematically around twice the percentage of the included obsolete ones, but with a large 95% credible interval. The results have implications for both research and practice in that the found systematic error should be accounted for in both studies on software estimation and, maybe more importantly, in estimation practices to avoid over-estimations due to this systematic error. We partly explain this error to be stemming from the cognitive bias of anchoring-and-adjustment, i.e. the obsolete requirements anchored a much larger software. However, further studies are needed in order to accurately predict this effect. © 2021, The Author(s).
25.	Joshi, P., et al. (författare) Impact of usability on process lead-time in information systems: A case study 2019 Ingår i: Journal of Systems and Software. - : Elsevier BV. - 0164-1212. ; 148, s. 148-169 Tidskriftsartikel (refereegranskat)abstract Technological advancements have started to demand the need for information systems to survive in the business world. There is an inherent need to be fast and efficient to conquer the market. In order to reduce time to market there is a need to shorten the lead-time in design and development process of products. Hence, lead-time is a significant performance metric for a product development organizations having information systems. It is important to explore the factors which affect the process lead-time in information systems. The objective of this study is to explore the impact that usability (one of the factors that may affect the process lead-time) has on process lead-time. This paper presents a case study involving qualitative and quantitate data from Volvo Group, which uses an information system called KOLA for their design and development process. Data was collected through 29 interviews, 17 think aloud sessions, 5 document studies, and 73 responses from a survey. This study identifies which usability factors and heuristics that have an impact on process lead-time. Moreover, the results show that the users level of experience determines the effective utilization of accelerators and thereby affecting the process lead-time. Finally, usability plays an important role in shortening the process lead-time in information systems. © 2018 Elsevier Inc.
26.	Magazinius, Ana, 1979, et al. (författare) Effects of Feature Complexity on Software Effort Estimates - an Exploratory Study 2014 Ingår i: 40th Euromicro Conference on Software Engineering and Advanced Applications, August 27-29, 2014, Verona, Italy. - 1089-6503. - 9781479957958 ; , s. 301-304 Konferensbidrag (refereegranskat)abstract Software estimates are an important input to project selection, planning, monitoring as well assessment of projects’ success. However, the practice of estimation is also a challenging activity for many practitioners, and there is a continuing need to understand and improve it. To contribute to the existing knowledge of this process, an in-depth study was conducted where 18 practitioners from eight subdomains at a company producing embedded systems were interviewed. The contribution of this article is twofold: First, it reports the estimation challenges as perceived by the practitioners where the two most prominent were organizational dependencies and complexity of requested features. Second, since feature complexity was noted as one of the estimation challenges, this paper also reports on factors that are driving that complexity, two of the most common being dependencies on functionality developed by other parts of the organization, and functionality that affects the entire product.
27.	Ouriques, R. A. B., et al. (författare) Knowledge Management Strategies and Processes in Agile Software Development: A Systematic Literature Review 2019 Ingår i: International Journal of Software Engineering and Knowledge Engineering. - : World Scientific Pub Co Pte Lt. - 0218-1940 .- 1793-6403. ; 29:3, s. 345-380 Tidskriftsartikel (refereegranskat)abstract Knowledge-intensive companies that adopt Agile Software Development (ASD) rely on efficient implementation of Knowledge Management (KM) strategies to promote different Knowledge Processes (KPs) to gain competitive advantage. This study aims to explore how companies that adopt ASD implement KM strategies utilizing practices that promote the KPs in the different organizational layers. Through a systematic literature review, we analyzed 32 primary studies, selected by automated search and snowballing in the extant literature. To analyze the data, we applied narrative synthesis. Most of the identified KM practices implement personalization strategies (81%), supported by codification (19%). Our review shows that the primary studies do not report KM practices in the strategic layer and two of them in the product portfolio layer; on the other hand, in the project layer, the studies report 33 practices that implement personalization strategy, and seven practices that implement codification. KM strategies in ASD promote mainly the knowledge transfer process with practices that stimulates social interaction to share tacit knowledge in the project layer. As a result of using informal communication, a significant amount of knowledge can be lost or not properly transferred to other individuals and, instead of propagating the knowledge, it remains inside a few individuals' minds.
28.	Ouriques, Raquel, et al. (författare) Continuous Assimilation of Change in Agile Software Development : An empirical study on the role of the knowledge-based resources Annan publikation (övrigt vetenskapligt/konstnärligt)abstract As the software value chain is knowledge-based due to the high dependency on people, the lack of practice to manage knowledge as a resource might jeopardize its application in software development. The resource-based view of the firm provides a different perspective on the utilization of knowledge, assisting the identification of the Knowledge-Based Resources (KBRs) that allow a company to have a continuous readiness to quickly respond to the market changes. To understand how the KBRs support coordination in Agile Software Development (ASD), we applied a grounded theory approach, collecting data from 18 practitioners, coming from five companies. As results, we identified 44 KBRs that were grouped in the Continuous Assimilation Model (CHASM). They support coordination in ASD with continuous assimilation of change which is supported by people’s business analytic perspective and product systemic reasoning. The companies are able to utilize a certain level of their KBRs through social collaboration and team environment/settings. However, the inefficient utilization of these resources results in a significant knowledge loss. Furthermore, CHASM points out areas where practitioners can establish strategies based on the priorities that the companies give to the investigated KBRs, as well as a set of research opportunities for future investigation.
29.	Ouriques, Raquel, et al. (författare) Knowledge Management Strategies and Processes in Agile Software Development: A Systematic Literature Review 2019 Ingår i: International Journal of Software Engineering and Knowledge Engineering. - : World Scientific. - 0218-1940. ; 29:3 Tidskriftsartikel (refereegranskat)abstract Knowledge-intensive companies that adopt Agile Software Development (ASD) rely on efficient implementation of Knowledge Management (KM) strategies to promote different Knowledge Processes (KPs) to gain competitive advantage. This study aims to explore how companies that adopt ASD implement KM strategies utilizing practices that promote the KPs in the different organizational layers. Through a systematic literature review, we analyzed 32 primary studies, selected by automated search and snowballing in the extant literature. To analyze the data, we applied narrative synthesis. Most of the identified KM practices implement personalization strategies (81%), supported by codification (19%). Our review shows that the primary studies do not report KM practices in the strategic layer and two of them in the product portfolio layer; on the other hand, in the project layer, the studies report 33 practices that implement personalization strategy, and seven practices that implement codification. KM strategies in ASD promote mainly the knowledge transfer process with practices that stimulates social interaction to share tacit knowledge in the project layer. As a result of using informal communication, a significant amount of knowledge can be lost or not properly transferred to other individuals and, instead of propagating the knowledge, it remains inside a few individuals' minds.
30.	Ouriques, Raquel, et al. (författare) The role of knowledge-based resources in Agile Software Development contexts 2023 Ingår i: Journal of Systems and Software. - : Elsevier. - 0164-1212 .- 1873-1228. ; 197 Tidskriftsartikel (refereegranskat)abstract The software value chain is knowledge-based since it is highly dependant on people. Consequently, a lack of practice in managing knowledge as a resource may jeopardise its application in software development. Knowledge-Based Resources (KBRs) relate to employees’ intangible knowledge that is deemed to be valuable to a company's competitive advantage. In this study, we apply a grounded theory approach to examine the role of KBRs in Agile Software Development (ASD). To this aim, we collected data from 18 practitioners from five companies. We develop the Knowledge-Push theory, which explains how KBRs boost the need for change in ASD. Our results show that the practitioners who participated in the study utilise, as primary strategies, task planning, resource management, and social collaboration. These strategies are implemented through the team environment and settings and incorporate an ability to codify and transmit knowledge. However, this process of codification is non-systematic, which consequently introduces inefficiency in the domain of knowledge resource utilisation, resulting in potential knowledge waste. This inefficiency can generate negative implications for software development, including meaningless searches in databases, frustration because of recurrent problems, the unnecessary redesign of solutions, and a lack of awareness of knowledge sources. © 2022 The Authors
31.	Ouriques, Raquel, et al. (författare) Thinking strategically about knowledge management in agile software development 2018 Ingår i: Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics). - Cham : Springer Verlag. - 0302-9743 .- 1611-3349. - 9783030036720 ; 11271 LNCS, s. 389-395 Konferensbidrag (refereegranskat)abstract Agile methodologies gave teams more autonomy regarding planning tasks and executing them. As a result, coordination gets more flexible, but much relevant knowledge remains undocumented and inside teams’ borders, due to informal communication and reduced development documentation. Since knowledge plays an essential role in software development, it is important to have effective knowledge management (KM) practices that contribute to a better knowledge resource allocation. Several KM practices have been reported in empirical studies in Agile Software Development (ASD). However, these practices are not evaluated regarding its effectiveness or how do they affect product quality. Besides, the studies do not demonstrate connections between the KM practices in the project level and the strategic level. The lack of connection between these levels can result in deviations from the company’s corporate strategy, wasted resources and irrelevant knowledge acquisition. This paper discusses how the strategic management can contribute to an integrated approach to KM in ASD; considering the organizational structure and the corporate strategy. Based on this discussion, we propose research areas that may help with planning KM strategies that can have their effectiveness measured and contribute to product quality. © Springer Nature Switzerland AG 2018.
32.	Ouriques, Raquel (författare) Understanding and Supporting Knowledge Management in Agile Software Development 2019 Licentiatavhandling (övrigt vetenskapligt/konstnärligt)abstract Background. Agile Software Development (ASD) promises agility and flexibility in dealing with uncertainty by prioritizing interaction between people supported by informal communication and knowledge sharing. The lack of practices to manage the knowledge as a resource might jeopardize the application of knowledge in the production of goods and service. The utilization of Knowledge Management (KM) strategies can significantly support achieving and sustaining competitive advantage and brings several benefits to software development. However, how to manage knowledge in ASD is still not well understood or investigated. Objectives. The main objective of this thesis is to contribute to the software engineering field by providing a different perspective on directions that KM can take to improve knowledge-based resource (KBR) management in ASD. The detailed objectives are: (i) Understand the current ASD environment regarding KM; (ii) Identify KBRs in ASD and its implications for KM; and (iii) Provide an initial set of variables to evaluate knowledge criticality of knowledge items in ASD. Method. We used a mixed-methods approach to address the objective of this thesis. The methods selected to conduct the studies include systematic literature review, grounded theory, and improvement case study. The data collection comprised a literature review, semi-structured interviews, and practitioners’ feedback through static validation. Results. From our SLR we observed that that KM strategies in ASD promote mainly knowledge transfer through practices that stimulate social interaction to share tacit knowledge in the project layer, increasing the risk of losing knowledge by keeping the knowledge localized inside a few individual’s minds. When it comes to coordination, practitioners utilize KBRs in their routines, through social collaboration within teams’ environment/settings. However, this process is nonsystematic, which brings inefficiency to KBR utilization resulting in knowledge loss. It can generate negative implications to the course of the software development, including meaningless searches in databases, frustration because of recurrent problems, and unawareness of knowledge sources. To support decision making related to knowledge retention, we have developed an initial version of the method to evaluate the criticality (KCEM) of a knowledge item, which is divided into two categories, relevance, and scarcity. Conclusion. The current results of this thesis are of particular interest. However, we recognize that the work is unfinished. As a complement to this thesis, we have planned our long-term objective, which is to contribute to creating scalable KM solutions for companies adopting ASD.We divide this long-term objective into three studies: Carry out a complementary study to apply KCEM in different companies; explore efficient ways of storing codified knowledge in combination with the KCEM, and investigate how to define metrics to evaluate the outcomes of KM practices.

Skapa referenser, mejla, bekava och länka

Länka till träfflistan

Träfflista för sökning "WFRF:(Berntsson Svensson Richard 1978) "

Avgränsa träffmängd

År