An experiment with a release planning method for web application development

Authors:
Sven Ziemer;Ilaria Canova Calori
Affiliations:
Department of Computer and Information Science, Norwegian University of Science and Technology, Trondheim, Norway;Department of Computer and Information Science, Norwegian University of Science and Technology, Trondheim, Norway
Venue:
EuroSPI'07 Proceedings of the 14th European conference on Software Process Improvement
Year:
2007

Citing 7
Cited 1

Experimentation in software engineering: an introduction

Experimentation in software engineering: an introduction
A Cost-Value Approach for Prioritizing Requirements

IEEE Software
Optimizing Value and Cost in Requirements Analysis

IEEE Software
An Estimation-Based Management Framework for Enhancive Maintenance in Commercial Software Products

ICSM '02 Proceedings of the International Conference on Software Maintenance (ICSM'02)
Supporting Software Release Planning Decisions for Evolving Systems

SEW '05 Proceedings of the 29th Annual IEEE/NASA on Software Engineering Workshop
A family of empirical studies to compare informal and optimization-based planning of software releases

Proceedings of the 2006 ACM/IEEE international symposium on Empirical software engineering
Ad hoc versus systematic planning of software releases – a three-staged experiment

PROFES'06 Proceedings of the 7th international conference on Product-Focused Software Process Improvement

A systematic review on strategic release planning models

Information and Software Technology

Quantified Score

Hi-index	0.00

Visualization

Abstract

Web application development is under certain circumstances such as a strong emphasis on time-to-market characterised by the usage of informal and ad-hoc development practices and a lot of tacit knowledge. Here we present an experiment that has been carried out in order to evaluate a recently proposed release planning method for web application development. This method aims at bringing stakeholders together to share knowledge and to decide on a configuration for the next release that satisfies all stakeholders. The method has been evaluated in terms of its effect on factors such as knowledge sharing, understanding, support to reach a consensus and stakeholders satisfaction.