Marjo Kauppinen
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Previous Organizations / Institutes
The organizations / institutes from the scholar's other articles in the past ten years
Research Subjects
Marjo Kauppinen has a total of 56 co-authors. Here are the top co-authors by number of shared publications:
- Sari Kujala
Department of Computer Science, Aalto University, Espoo, Finland
12 shared publications Marko Komssi
Aalto University, PO Box 9210, Espoo, Finland
7 shared publications- Tomi Männistö
University of Helsinki
6 shared publications Laura Lehtola
Aalto University, PO Box 9210, Espoo, Finland
4 shared publicationsHarri Tohonen
Aalto University, PO Box 9210, Espoo, Finland
3 shared publicationsL. Lehtola
Inst. of Software Bus. & Eng., Helsinki Univ. of Technol., Finland
3 shared publications
Latest Publications
- 23 March 2025
- Published by Springer Nature
- p. 324-339
Data-Limited Continuous Experimentation (dlCE): A Literature Review
- 23 March 2025
- Published by Springer Nature
- p. 324-339
Data-Limited Continuous Experimentation (dlCE): A Literature Review
- 30 March 2024
- Published by Springer Nature
- p. 129-146
Candidate Solutions for Defining Explainability Requirements of AI Systems
- 30 March 2024
- Published by Springer Nature
- p. 129-146
Candidate Solutions for Defining Explainability Requirements of AI Systems
- Open Access
- 1 January 2018
- Published by IOS Press
- Vol. 247, 196-200
Designing an E-Learning Application to Facilitate Health Care Professionals' Cross-Cultural Communication
In recent times, health care professionals (HCP) have come across a number of migrants as their patients. The cultural differences lead to communicational challenges between the migrant patients and health care professionals. Our project aimed to discover HCPs' attitudes, challenges and needs on cross-cultural communication, so that we can develop an e-learning solution that would be helpful for them. By conducting interviews with HCPs, we identified five crucial categories of problems and the current solutions that experienced professionals use to tackle those problems. These interviews also helped us in understanding the motivational factors of HCPs, when using e-learning application. Health care professionals prefer a focus on examples and themes such as death and pain that they face in their everyday work. Changing attitudes by e-learning application is challenging. However, e-learning was recognized as a flexible way for supporting traditional training with HCPs who are busy at work most of the time.
- 1 January 2018
- Published by IOS Press
- Vol. 247, 196-200
Open AccessDesigning an E-Learning Application to Facilitate Health Care Professionals' Cross-Cultural Communication
In recent times, health care professionals (HCP) have come across a number of migrants as their patients. The cultural differences lead to communicational challenges between the migrant patients and health care professionals. Our project aimed to discover HCPs' attitudes, challenges and needs on cross-cultural communication, so that we can develop an e-learning solution that would be helpful for them. By conducting interviews with HCPs, we identified five crucial categories of problems and the current solutions that experienced professionals use to tackle those problems. These interviews also helped us in understanding the motivational factors of HCPs, when using e-learning application. Health care professionals prefer a focus on examples and themes such as death and pain that they face in their everyday work. Changing attitudes by e-learning application is challenging. However, e-learning was recognized as a flexible way for supporting traditional training with HCPs who are busy at work most of the time.
- 28 October 2017
- Published by Springer Nature
- p. 55-70
What Can Be Learnt from Experienced Data Scientists? A Case Study
- 28 October 2017
- Published by Springer Nature
- p. 55-70
What Can Be Learnt from Experienced Data Scientists? A Case Study
- 1 August 2016
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- Vol. 44, 94-103
An Iterative Process to Connect Business and IT Development: Lessons Learned
Combining business and IT viewpoints in large development projects is a big challenge for many organizations in the outsourced environment. The goal of this paper is to describe process and good practices that can support a case-study organization in connecting business and IT development during the requirements definition. The results are based on 17 interviews, an analysis of 15 large projects, process improvement meetings, validation workshops, and a survey. We first identified the lessons learned of the past projects and then defined good practices to be used in future projects. This paper describes a new process to be used by the customer organization and its suppliers in the outsourced IT development environment. The principal idea is to iteratively improve the requirements during the pre-study, procurement, and implementation phases of the project. To strengthen the link between business and IT development, the process also contains activities and good practices related to development-goals setting, innovation and business development, business-case analysis, solution planning and enterprise architecture modeling. The results indicate that the requirements definition should be not only part of the IT system development but also closely integrated with the business development of the customer organization.
- 1 August 2016
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- Vol. 44, 94-103
An Iterative Process to Connect Business and IT Development: Lessons Learned
Combining business and IT viewpoints in large development projects is a big challenge for many organizations in the outsourced environment. The goal of this paper is to describe process and good practices that can support a case-study organization in connecting business and IT development during the requirements definition. The results are based on 17 interviews, an analysis of 15 large projects, process improvement meetings, validation workshops, and a survey. We first identified the lessons learned of the past projects and then defined good practices to be used in future projects. This paper describes a new process to be used by the customer organization and its suppliers in the outsourced IT development environment. The principal idea is to iteratively improve the requirements during the pre-study, procurement, and implementation phases of the project. To strengthen the link between business and IT development, the process also contains activities and good practices related to development-goals setting, innovation and business development, business-case analysis, solution planning and enterprise architecture modeling. The results indicate that the requirements definition should be not only part of the IT system development but also closely integrated with the business development of the customer organization.
- 1 August 2015
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- No. 1090705X,p. 334-343
Agile requirements engineering with prototyping: A case study
The rise of agile software development methods has led to the abandonment of many traditional practices especially in requirements engineering (RE). Agile RE is still a relatively new research area and the growing use of agile methods in large projects is forcing companies to look for more formal practices for RE. This paper describes experiences gained from a case study of a large agile project. The goal of this case study was to explore how prototyping can solve the challenges of agile RE. Our findings indicate that while prototyping can help with some challenges of agile RE such as lack of documentation, motivation for RE work and poor quality communication, it also needs complementary practices to reach its full potential. These practices include reviewing the big picture regularly, keeping track of quality requirements, and using ATDD (Acceptance Test Driven Development).
- 1 August 2015
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- No. 1090705X,p. 334-343
Agile requirements engineering with prototyping: A case study
The rise of agile software development methods has led to the abandonment of many traditional practices especially in requirements engineering (RE). Agile RE is still a relatively new research area and the growing use of agile methods in large projects is forcing companies to look for more formal practices for RE. This paper describes experiences gained from a case study of a large agile project. The goal of this case study was to explore how prototyping can solve the challenges of agile RE. Our findings indicate that while prototyping can help with some challenges of agile RE such as lack of documentation, motivation for RE work and poor quality communication, it also needs complementary practices to reach its full potential. These practices include reviewing the big picture regularly, keeping track of quality requirements, and using ATDD (Acceptance Test Driven Development).
- 14 March 2015
- Published by Springer Nature
- p. 214-229
Challenges of the Customer Organization’s Requirements Engineering Process in the Outsourced Environment – A Case Study
- 14 March 2015
- Published by Springer Nature
- p. 214-229
Challenges of the Customer Organization’s Requirements Engineering Process in the Outsourced Environment – A Case Study
- 1 August 2014
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- No. 1090705X,p. 283-292
Evaluating the business value of information technology: Case study on game management system
Evaluating the multidimensional and dynamic nature of IT business value is a continuous challenge. This paper examines how system dynamics can be used in evaluating IT business value in a company level. We approach IT business value as a web of impacts, where benefits and sacrifices are ultimately evaluated against company earnings logic. This study is based on an action research and covers a pilot project within two co-operating companies. System dynamics was utilised to construct a value creation model for an existing Gaming Management System. This value creation modelling covered two dimensions: 1) structural evaluation of IT impacts with cause-and-effect models, 2) dynamic evaluation and simulation of value realisation over time. As a result, value creation modelling was able to provide a visual overview of how IT impacts were linked to business value through value paths, and how much and when value was realised. Value creation modelling enabled prototyping of value realisation that can provide value based insights for development activities like requirements elicitation and analysis. The examined approach proved its potential for providing a common language for technology and business parties, thus improving IT business alignment.
- 1 August 2014
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- No. 1090705X,p. 283-292
Evaluating the business value of information technology: Case study on game management system
Evaluating the multidimensional and dynamic nature of IT business value is a continuous challenge. This paper examines how system dynamics can be used in evaluating IT business value in a company level. We approach IT business value as a web of impacts, where benefits and sacrifices are ultimately evaluated against company earnings logic. This study is based on an action research and covers a pilot project within two co-operating companies. System dynamics was utilised to construct a value creation model for an existing Gaming Management System. This value creation modelling covered two dimensions: 1) structural evaluation of IT impacts with cause-and-effect models, 2) dynamic evaluation and simulation of value realisation over time. As a result, value creation modelling was able to provide a visual overview of how IT impacts were linked to business value through value paths, and how much and when value was realised. Value creation modelling enabled prototyping of value realisation that can provide value based insights for development activities like requirements elicitation and analysis. The examined approach proved its potential for providing a common language for technology and business parties, thus improving IT business alignment.
- 1 August 2014
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 16-17
A/B testing: A promising tool for customer value evaluation
This paper aims to describe the use of A/B testing, a method used in web-development and position it in the context of the requirements engineering process and customer value evaluation. We propose that A/B testing can complement qualitative user research and offer a potential way to validate the value which system improvements bring to customers. Finally, we discuss our research plan for investigating the use of A/B testing in company contexts.
- 1 August 2014
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 16-17
A/B testing: A promising tool for customer value evaluation
This paper aims to describe the use of A/B testing, a method used in web-development and position it in the context of the requirements engineering process and customer value evaluation. We propose that A/B testing can complement qualitative user research and offer a potential way to validate the value which system improvements bring to customers. Finally, we discuss our research plan for investigating the use of A/B testing in company contexts.