A Revelatory Case Study on Scaling Agile Release Planning
- 1 September 2010
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 289-296
Abstract
A way to scale up agile release planning to meet the requirements of multi-team agile development is a practice called joint release planning. A software product company piloted the joint release planning method. The aim of the company was to improve coordination of work of multiple agile development teams who develop a large legacy software product. Another aim was to improve communication between product management and development. We conducted a case study to explore how the new release planning method was executed. We gathered data by observing two release planning events, observing event planning meetings, and by conducting surveys. The events were attended by approximately 140 stakeholders, including over 10 development teams, who spent several days in a common space. The participants liked the method and considered it efficient. This revelatory case study provides the first detailed empirical description of this emerging method for multi-team agile release planning.Keywords
This publication has 11 references indexed in Scilit:
- A systematic review on strategic release planning modelsInformation and Software Technology, 2010
- The impact of agile principles on market‐driven software product developmentJournal of Software Maintenance and Evolution: Research and Practice, 2010
- The Agile Requirements Refinery: Applying SCRUM Principles to Software Product Management2009
- A survey study of critical success factors in agile software projectsJournal of Systems and Software, 2008
- Agile Requirements Engineering Practices: An Empirical StudyIEEE Software, 2008
- A systematic approach for solving the wicked problem of software release planningSoft Computing, 2007
- Strategic Release Planning and Evaluation of Operational Feasibility2005
- Release Planning in Market-Driven Software Product Development: Provoking an UnderstandingRequirements Engineering, 2002
- 4CC: A Framework for Managing Software Product DevelopmentEngineering Management Journal, 2002
- Requirements that handle IKIWISI, COTS, and rapid changeComputer, 2000