Change search
Link to record
Permanent link

Direct link
BETA
Gorschek, Tony
Publications (10 of 127) Show all publications
Ouriques, R., Britto, R., Wnuk, K., Ouriques, J. F. & Gorschek, T. (2019). A Method to Evaluate Knowledge Resources in Agile Software Development. In: Proceeding of The ACM/IEEE International Symposium on Empirical Software Engineering and Measurement ESEM 2019: . Paper presented at The ACM/IEEE International Symposium on Empirical Software Engineering and Measurement ESEM 2019 Porto de Galinhas, Brazil September 19th-20th, 2019. IEEE
Open this publication in new window or tab >>A Method to Evaluate Knowledge Resources in Agile Software Development
Show others...
2019 (English)In: Proceeding of The ACM/IEEE International Symposium on Empirical Software Engineering and Measurement ESEM 2019, IEEE, 2019Conference paper, Published paper (Refereed)
Abstract [en]

Background: Organizations adopting Agile Software Development (ASD) use different Knowledge Management (KM) practices to retain and share knowledge. However, it is often the case that knowledge retention is carried out in an ad-hoc way.

Aims: In this study, we report our experience from proposing the Knowledge Critically Evaluation Method (KCEM) to evaluate knowledge items (KIT). Our main goal with KCEMs is to support companies to systematically retain knowledge in ASD contexts.

Method: We conducted an improvement case study to develop and evaluate KCEM. This research follows the guidelines for technology transfer between industry and academia. The case and unit of analysis is Ericsson, a Swedish company that develops telecommunication solutions.

Results: In this paper, we provide initial results of both lab and static validation, enriched by the lessons learned.

Conclusions: The preliminary results show that KCEM is easy to understand and use, provides a different perspective on the KIT by visualizing in the criticality chart, and reduces the level of abstraction associated to a knowledge subject area.

Place, publisher, year, edition, pages
IEEE, 2019
Keywords
Agile Software Development, Critical Knowledge, Knowledge Management
National Category
Computer Systems
Identifiers
urn:nbn:se:bth-18507 (URN)978-1-7281-2968-6 (ISBN)
Conference
The ACM/IEEE International Symposium on Empirical Software Engineering and Measurement ESEM 2019 Porto de Galinhas, Brazil September 19th-20th, 2019
Projects
S.E.R.T. Research Profile
Available from: 2019-08-01 Created: 2019-08-01 Last updated: 2019-09-06Bibliographically approved
Klotins, E., Unterkalmsteiner, M., Chatzipetrou, P., Gorschek, T., Prikladniki, R., Tripathi, N. & Pompermaier, L. B. (2019). A progression model of software engineering goals, challenges, and practices in start-ups. IEEE Transactions on Software Engineering
Open this publication in new window or tab >>A progression model of software engineering goals, challenges, and practices in start-ups
Show others...
2019 (English)In: IEEE Transactions on Software Engineering, ISSN 0098-5589, E-ISSN 1939-3520Article in journal (Refereed) Epub ahead of print
Abstract [en]

Context: Software start-ups are emerging as suppliers of innovation and software-intensive products. However, traditional software engineering practices are not evaluated in the context, nor adopted to goals and challenges of start-ups. As a result, there is insufficient support for software engineering in the start-up context. IEEE

Place, publisher, year, edition, pages
Institute of Electrical and Electronics Engineers Inc., 2019
Keywords
Analytical models, Companies, Market opportunities, progression model, Requirements engineering, Software, Software engineering, software engineering practices, software start-up, Computer software, Industry
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-17706 (URN)10.1109/TSE.2019.2900213 (DOI)2-s2.0-85061979918 (Scopus ID)
Available from: 2019-03-07 Created: 2019-03-07 Last updated: 2019-09-26Bibliographically approved
Olsson, T., Wnuk, K. & Gorschek, T. (2019). An empirical study on decision making for quality requirements. Journal of Systems and Software, 149, 217-233
Open this publication in new window or tab >>An empirical study on decision making for quality requirements
2019 (English)In: Journal of Systems and Software, ISSN 0164-1212, E-ISSN 1873-1228, Vol. 149, p. 217-233Article in journal (Refereed) Published
Abstract [en]

Context: Quality requirements are important for product success yet often handled poorly. The problems with scope decision lead to delayed handling and an unbalanced scope. Objective: This study characterizes the scope decision process to understand influencing factors and properties affecting the scope decision of quality requirements. Method: We studied one company's scope decision process over a period of five years. We analyzed the decisions artifacts and interviewed experienced engineers involved in the scope decision process. Results: Features addressing quality aspects explicitly are a minor part (4.41%) of all features handled. The phase of the product line seems to influence the prevalence and acceptance rate of quality features. Lastly, relying on external stakeholders and upfront analysis seems to lead to long lead-times and an insufficient quality requirements scope. Conclusions: There is a need to make quality mode explicit in the scope decision process. We propose a scope decision process at a strategic level and a tactical level. The former to address long-term planning and the latter to cater for a speedy process. Furthermore, we believe it is key to balance the stakeholder input with feedback from usage and market in a more direct way than through a long plan-driven process. © 2018 Elsevier Inc.

Place, publisher, year, edition, pages
Elsevier Inc., 2019
Keywords
Non-functional requirements, Product management, Quality requirements, Requirements engineering, Requirements scope decision, Hardware, Software engineering, Decision process, Empirical studies, External stakeholders, Long term planning, Decision making
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-17455 (URN)10.1016/j.jss.2018.12.002 (DOI)000457951800009 ()2-s2.0-85058167239 (Scopus ID)
Available from: 2019-01-09 Created: 2019-01-09 Last updated: 2019-02-21Bibliographically approved
Alahyari, H., Gorschek, T. & Berntsson Svensson, R. (2019). An exploratory study of waste in software development organizations using agile or lean approaches: A multiple case study at 14 organizations. Information and Software Technology, 107, 78-94
Open this publication in new window or tab >>An exploratory study of waste in software development organizations using agile or lean approaches: A multiple case study at 14 organizations
2019 (English)In: Information and Software Technology, ISSN 0950-5849, E-ISSN 1873-6025, Vol. 107, p. 78-94Article in journal (Refereed) Published
Abstract [en]

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.

Place, publisher, year, edition, pages
Elsevier B.V., 2019
Keywords
Agile software development, Lean software development, Non-value adding activities, Waste, Wastes, Empirical studies, Exploratory studies, Long-term perspective, Multiple-case study, Software development organizations, Value adding activities, Software design
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-17085 (URN)10.1016/j.infsof.2018.08.006 (DOI)000452586900006 ()2-s2.0-85053629776 (Scopus ID)
Available from: 2018-10-05 Created: 2018-10-05 Last updated: 2019-01-09Bibliographically approved
Berntsson Svensson, R., Gorschek, T., Bengtsson, P. & Widerberg, J. (2019). BAM: backlog assessment method. In: Lect. Notes Bus. Inf. Process.: . Paper presented at 20th International Conference on Agile Software Development, XP 2019; Montreal; Canada; 21 May 2019 through 25 May (pp. 53-68). Springer Verlag, 355
Open this publication in new window or tab >>BAM: backlog assessment method
2019 (English)In: Lect. Notes Bus. Inf. Process., Springer Verlag , 2019, Vol. 355, p. 53-68Conference paper, Published paper (Refereed)
Abstract [en]

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.

Place, publisher, year, edition, pages
Springer Verlag, 2019
Series
Lecture Notes in Business Information Processing, ISSN 1865-1348
Keywords
Agile, Backlog assessment method, Case study, Software process assessment, Software process improvement, Process engineering, Agile organizations, Industrial environments, Software process improvements, Software products, Software design
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-18010 (URN)10.1007/978-3-030-19034-7_4 (DOI)2-s2.0-85065868875 (Scopus ID)9783030190330 (ISBN)
Conference
20th International Conference on Agile Software Development, XP 2019; Montreal; Canada; 21 May 2019 through 25 May
Note

open access

Available from: 2019-06-13 Created: 2019-06-13 Last updated: 2019-06-13Bibliographically approved
Alégroth, E., Gorschek, T., Petersen, K. & Mattsson, M. (2019). Characteristics that affect Preference of DecisionModels for Asset Selection: An Industrial Questionnaire Survey - Appendix A: Questionnaire Introduction. Decision-making in Practice / Appendix B: Survey results.
Open this publication in new window or tab >>Characteristics that affect Preference of DecisionModels for Asset Selection: An Industrial Questionnaire Survey - Appendix A: Questionnaire Introduction. Decision-making in Practice / Appendix B: Survey results
2019 (English)Data set, Aggregated data
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-18692 (URN)
Available from: 2019-09-25 Created: 2019-09-25 Last updated: 2019-09-25
Badampudi, D., Wohlin, C. & Gorschek, T. (2019). Contextualizing research evidence through knowledge translation in software engineering. In: ACM International Conference Proceeding Series: . Paper presented at 23rd Evaluation and Assessment in Software Engineering Conference, EASE Copenhagen, 14 April 2019 through 17 April 2019 (pp. 306-311). Association for Computing Machinery
Open this publication in new window or tab >>Contextualizing research evidence through knowledge translation in software engineering
2019 (English)In: ACM International Conference Proceeding Series, Association for Computing Machinery , 2019, p. 306-311Conference paper, Published paper (Refereed)
Abstract [en]

Usage of software engineering research in industrial practice is a well-known challenge. Synthesis of knowledge from multiple research studies is needed to provide evidence-based decision-support for industry. The objective of this paper is to present a vision of how a knowledge translation framework may look like in software engineering research, in particular how to translate research evidence into practice by combining contextualized expert opinions with research evidence. We adopted the framework of knowledge translation from health care research, adapted and combined it with a Bayesian synthesis method. The framework provided in this paper includes a description of each step of knowledge translation in software engineering. Knowledge translation using Bayesian synthesis intends to provide a systematic approach towards contextualized, collaborative and consensus-driven application of research results. In conclusion, this paper contributes towards the application of knowledge translation in software engineering through the presented framework. © 2019 Association for Computing Machinery.

Place, publisher, year, edition, pages
Association for Computing Machinery, 2019
Keywords
Bayesian synthesis, Decision-making, Knowledge translation, Application programs, Decision making, Decision support systems, Industrial research, Bayesian, Evidence- based decisions, Expert opinion, Industrial practices, Multiple research, Research results, Synthesis method, Engineering research
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-17891 (URN)10.1145/3319008.3319358 (DOI)2-s2.0-85064754769 (Scopus ID)9781450371452 (ISBN)
Conference
23rd Evaluation and Assessment in Software Engineering Conference, EASE Copenhagen, 14 April 2019 through 17 April 2019
Available from: 2019-05-21 Created: 2019-05-21 Last updated: 2019-05-21Bibliographically approved
Pernstal, J., Feldt, R., Gorschek, T. & Floren, D. (2019). FLEX-RCA: a lean-based method for root cause analysis in software process improvement. Software quality journal, 27(1), 389-428
Open this publication in new window or tab >>FLEX-RCA: a lean-based method for root cause analysis in software process improvement
2019 (English)In: Software quality journal, ISSN 0963-9314, E-ISSN 1573-1367, Vol. 27, no 1, p. 389-428Article in journal (Refereed) Published
Abstract [en]

Software process improvement (SPI) is an instrument to increase the productivity of, and the quality of work, in software organizations. However, a majority of SPI frameworks are too extensive or provide guidance and potential improvement areas at a high level, indicating only the symptoms, not the causes. Motivated by the industrial need of two Swedish automotive companies to systematically uncover the underlying root causes of high-level improvement issues identified in an SPI project-assessing inter-departmental interactions in large-scale software systems development-this paper advances a root cause analysis (RCA) method building on Lean Six Sigma, called Flex-RCA. Flex-RCA is used to delve deeper into challenges identified to find root causes as a part of the evaluation and subsequent improvement activities. We also demonstrate and evaluate Flex-RCA's industrial applicability in a case study. An overall conclusion is that the use of Flex-RCA was successful, showing that it had the desired effect of both producing a broad base of causes on a high level and, more importantly, enabling an exploration of the underlying root causes.

Place, publisher, year, edition, pages
SPRINGER, 2019
Keywords
Organizational management and coordination, Communication, Software engineering, Software-intensive systems, Automotive industry, Case study, Lean product development, Agile, Process improvement
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-17827 (URN)10.1007/s11219-018-9408-8 (DOI)000462236000011 ()
Available from: 2019-04-18 Created: 2019-04-18 Last updated: 2019-04-24Bibliographically approved
Ouriques, R., Wnuk, K., Gorschek, T. & Berntsson Svensson, R. (2019). Knowledge Management Strategies and Processes in Agile Software Development: A Systematic Literature Review. International journal of software engineering and knowledge engineering, 29(3), 345-380
Open this publication in new window or tab >>Knowledge Management Strategies and Processes in Agile Software Development: A Systematic Literature Review
2019 (English)In: International journal of software engineering and knowledge engineering, ISSN 0218-1940, Vol. 29, no 3, p. 345-380Article, review/survey (Refereed) Published
Abstract [en]

Knowledge-intensive companies that adopt Agile Software Development (ASD) relay on efficient implementation of Knowledge Management (KM) strategies to promotes 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 stimulate 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.

Place, publisher, year, edition, pages
World Scientific, 2019
Keywords
knowledge management, agile software development
National Category
Engineering and Technology
Identifiers
urn:nbn:se:bth-17336 (URN)10.1142/S0218194019500153 (DOI)000462508200002 ()
Available from: 2018-11-26 Created: 2018-11-26 Last updated: 2019-08-01Bibliographically approved
Borg, M., Chatzipetrou, P., Wnuk, K., Alégroth, E., Gorschek, T., Papatheocharous, E., . . . Axelsson, J. (2019). Selecting component sourcing options: A survey of software engineering's broader make-or-buy decisions. Information and Software Technology, 112, 18-34
Open this publication in new window or tab >>Selecting component sourcing options: A survey of software engineering's broader make-or-buy decisions
Show others...
2019 (English)In: Information and Software Technology, ISSN 0950-5849, E-ISSN 1873-6025, Vol. 112, p. 18-34Article in journal (Refereed) Published
Abstract [en]

Context: Component-based software engineering (CBSE) is a common approach to develop and evolve contemporary software systems. When evolving a system based on components, make-or-buy decisions are frequent, i.e., whether to develop components internally or to acquire them from external sources. In CBSE, several different sourcing options are available: (1) developing software in-house, (2) outsourcing development, (3) buying commercial-off-the-shelf software, and (4) integrating open source software components. Objective: Unfortunately, there is little available research on how organizations select component sourcing options (CSO) in industry practice. In this work, we seek to contribute empirical evidence to CSO selection. Method: We conduct a cross-domain survey on CSO selection in industry, implemented as an online questionnaire. Results: Based on 188 responses, we find that most organizations consider multiple CSOs during software evolution, and that the CSO decisions in industry are dominated by expert judgment. When choosing between candidate components, functional suitability acts as an initial filter, then reliability is the most important quality. Conclusion: We stress that future solution-oriented work on decision support has to account for the dominance of expert judgment in industry. Moreover, we identify considerable variation in CSO decision processes in industry. Finally, we encourage software development organizations to reflect on their decision processes when choosing whether to make or buy components, and we recommend using our survey for a first benchmarking. © 2019

Place, publisher, year, edition, pages
Elsevier B.V., 2019
Keywords
Component-based software engineering, Decision making, Software architecture, Sourcing, Survey, Decision support systems, Open systems, Software design, Surveying, Surveys, Commercial off-the-shelf softwares, Industry practices, Make-or-buy decisions, Online questionnaire, Software development organizations, Software Evolution, Open source software
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-17871 (URN)10.1016/j.infsof.2019.03.015 (DOI)000469899100002 ()2-s2.0-85064013176 (Scopus ID)
Available from: 2019-05-02 Created: 2019-05-02 Last updated: 2019-06-20Bibliographically approved
Organisations

Search in DiVA

Show all publications