Collaborative value estimation in DevOps product management
Thesis event information
Date and time of the thesis defence
Place of the thesis defence
TA105, Linnanmaa Campus
Topic of the dissertation
Collaborative value estimation in DevOps product management
Doctoral candidate
Master of Science Henri Bomström
Faculty and unit
University of Oulu Graduate School, Faculty of Information Technology and Electrical Engineering, Software Engineering and Information Systems (SEIS)
Subject of study
Information Processing Science
Opponent
Professor Kari Smolander, Lappeenranta–Lahti University of Technology (LUT)
Custos
Docent Kari Liukkunen, University of Oulu
A shared view of feature value in DevOps software product management
Choosing what to build next is a key challenge for software companies. People can have different ideas about what makes a feature valuable, making decisions hard to explain and agree on. As software is updated more frequently, business and development teams need to work more closely together.
This thesis explores how to support that cooperation. Two case studies examined what information people involved in software development and management need. The research then focused on how teams assess the value of proposed features for software products. A planning tool with publicly available code was developed in collaboration with a company to support this work.
The findings show that people need a clearer view of how work is organised, as well as control over what information they use and when. A feature's value depends on several factors. Two stand out: how it depends on other features and how well it supports shared goals. Understanding these links can help teams discuss priorities and build a shared view of what is worth developing next.
This thesis explores how to support that cooperation. Two case studies examined what information people involved in software development and management need. The research then focused on how teams assess the value of proposed features for software products. A planning tool with publicly available code was developed in collaboration with a company to support this work.
The findings show that people need a clearer view of how work is organised, as well as control over what information they use and when. A feature's value depends on several factors. Two stand out: how it depends on other features and how well it supports shared goals. Understanding these links can help teams discuss priorities and build a shared view of what is worth developing next.
Created 19.10.2026 | Updated 19.10.2026