Seminar: Real-time Value Delivery in Software Engineering

Software Systems
Advanced studies
The goal of this seminar is to analyze existing approaches and experiences with respect to real time value delivery in software engineering, i.e., creating an research and development system that allows organizations to better decide what to develop and which strategies to follow. The students will get a comprehensive overview of modern experiment and feedback-driven software development.
Year Semester Date Period Language In charge
2014 spring 15.01-23.04. 3-4 English Jürgen Münch


Time Room Lecturer Date
Wed 14-16 C220 Jürgen Münch 15.01.2014-19.02.2014
Wed 14-16 C220 Jürgen Münch 12.03.2014-23.04.2014


“The quantum leap in software development speed by incrementally building and deploying software with real-time customer feedback will facilitate the speed and flexibility needed […]. Upon delivering the product or service, the focus shifts to creating incremental improvements, so that development cycles can be shortened, progress can be evaluated, and customer feedback and insight can be used to measure the value of the improvement and fed back to development in real-time.” [1]

There is a need in many software-based companies to evolve their software development practices towards continuous integration and continuous deployment. This allows a company to frequently and rapidly integrate and deploy their work and in consequence also opens opportunities for getting feedback from customers on a regular basis. Ideally, this feedback is used to support design decisions early in the development process, e.g., to determine which features should be maintained over time and which features should be skipped. In more general terms, the entire R&D system of an organization should be in a state where it is able to respond and act quickly based in instant customer feedback and where actual deployment of software functionality is seen as a way of fast experimenting and testing what the customer needs [2].

Experimentation refers here to fast validation of a business model or more specifically validating a value hypothesis. Reaching such a state of continuous experimentation implies a lot of challenges for organizations. Selected challenges are how to develop the “right” software while developing software “right”, how to have an appropriate tool infrastructure in place, how to measure and evaluate customer value, what are appropriate feedback systems, how to improve the velocity of software development, how to increase the business hit rate with new products and features, how to integrate such experiments into the development process, how to link knowledge about value for users or customers to higher-level goals of an organization. These challenges are quite new for many software-based organizations and not sufficiently understood from a software engineering perspective.

The goal of this seminar is to analyze existing approaches and experiences with respect to real time value delivery in software engineering, i.e., creating an R&D system that allows organizations to better decide what to develop and which strategies to follow. The students will get a comprehensive overview of modern experiment and feedback-driven software development.


Course News


Seminar Schedule
Date Topic
15.1.2014 Introduction
22.1.2014 Scientific writing and peer review
29.1.2014 No lecture
5.2.2014 Scientific presentations and oral communication, selection of topics, scheduling of presentations
12.2.2014 5 minute short presentations of topics
19.2.2014 No lecture / individual work
12.3.2014 No lecture / individual work
19.3.2014 No lecture / individual work
26.3.2014 No lecture / individual work
2.4.2014 Paper submission deadline
9.4.2014 Presentations I (Kallakivi, Sturaro, Hyvönen)
Peer paper review deadline
16.4.2014 Presentations II (Rissanen, Valén, Hirvikoski)
23.4.2014 Presentations III (Pennanen, Mäenpää, Kivi)
Final, revised paper version submission deadline

Seminar Paper Template

Seminar papers should be written using the IEEE conference template. Any writing tool can be used to write the paper as long as the outcome of the paper is PDF; IEEE templates are also offered in LaTex format for those interested. Download the template of your choosing, delete excess text from the template but preserve the format, input your information and start the graceful work of writing a paper.


Scientific conferences use conference platforms to facilitate the organization of conferences and manage paper submissions and anonymous reviews of program commitees. EasyChair is one of these platforms and this seminar will take advantage of conference services offered by EasyChair. Create an EasyChair account and log in to the 'Seminar on Real-time Value Delivery in Software Engineering' conference instance.


The Moodle virtual learning environment is available for use during the course. Moodle adds a new layer of communication between students and staff as peer discussions are possible in discussion forums. Everyone can post messages in the discussion forum and there is a possibility to use the enivornment for other course activities as well.

Completing the course

Each participant of the seminar will prepare a 6-8 page (IEEE template format) seminar paper on a topic related to real-time value delivery in software engineering. Participants will finally give a 20-30 minute presentation about their topic. The grade for the seminar will be based on both the seminar paper and the presentation.

All seminar papers have the same submission deadline on 2nd April. After the submission deadline, there will be a review round of the seminar papers. Other students and the course staff will give paper review comments and the authors should consider these comments for the final revised seminar paper which is due the 23rd of April. Seminar paper submissions will be done through the EasyChair conference platform. The course staff will distribute the seminar papers before the presentations to other participants so that participants can give feedback to presenters during the presentation sessions. Presentations should be uploaded on the day of the presentation.

Literature and material

[1] Strategic Research Agenda for Need for Speed, 2013,

[2] H. Olsson, H. Alahyari, and J. Bosch, “Climbing the stairway to heaven – a multiple- case study exploring barriers in the transition from agile development towards continuous deployment of software,” in Software Engineering and Advanced Applications (SEAA), 2012 38th EUROMICRO Conference on, 2012, pp. 392–399.

[3] A. Croll, B. Yoskowicz, "Lean Analytics: Use Data to Build a Better Startup Faster", O'Reilly, 2013.

[4] A. J. Smith, "The task of the referee." Computer 23.4 (1990): 65-71.

[5] David Lorge Parnas. 1998. Successful software engineering research. SIGSOFT Softw. Eng. Notes 23, 3 (May 1998), 64-68.

[6] Mary Shaw. 2003. Writing good software engineering research papers: minitutorial. In Proceedings of the 25th International Conference on Software Engineering (ICSE '03). IEEE Computer Society, Washington, DC, USA, 726-736.

[7] Andreas Zeller. How to Give a Good Research Talk. Master seminar presentation.

[8] B. Kitchenham and S. Charters, “Guidelines for performing systematic literature reviews in software engineering,” Keele University and Durham University Joint Report, Tech. Rep. EBSE 2007-001, 2007.

[9] Runeson, P., Host, M., Rainer, A., & Regnell, B. "Case study research in software engineering: Guidelines and examples", Wiley, 2012.