Continuous Release Planning in a Large-Scale Scrum Development Organization at Ericsson

Scrum development at large-scale requires a release planning process that supports the agile way of working and planning. Most of the existing release planning processes are plan-driven and ill suited for a large Scrum organization. This case study describes how release planning was conducted in a 350-person Scrum development organization with over 20 teams at Ericsson in 2011, and the related challenges and benefits. Data was collected with 39 interviews which were transcribed, coded and analysed. The release planning process was continuous and characterized by regular scoping and prioritization decisions, and by incremental elaboration of features. The challenges were the overcommitment caused by external pressure, managing non-feature specific work, and balancing between development efficiency and building generalist teams. The benefits were the increased flexibility and decreased development lead time, waste eliminated in the planning process, and increased developer motivation.

[1]  R. Feldt,et al.  A systematic review on strategic release planning models , 2010, Inf. Softw. Technol..

[2]  Reijo Sulonen,et al.  4CC: A Framework for Managing Software Product Development , 2002 .

[3]  Craig Larman,et al.  Practices for Scaling Lean & Agile Development: Large, Multisite, and Offshore Product Development with Large-Scale Scrum , 2010 .

[4]  Ken Schwaber,et al.  Agile Software Development with SCRUM , 2001 .

[5]  Dean Leffingwell,et al.  Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise , 2011 .

[6]  Richard Lyon,et al.  Scaling Up Pushing Scrum out of its Comfort Zone , 2008, Agile 2008 Conference.

[7]  Tsun Chow,et al.  A survey study of critical success factors in agile software projects , 2008, J. Syst. Softw..

[8]  Tony Gorschek,et al.  Social networks in software process improvement , 2010 .

[9]  Mike Cohn,et al.  Agile Estimating and Planning , 2005 .

[10]  Laura Lehtola,et al.  The challenge of release planning , 2011, 2011 Fifth International Workshop on Software Product Management (IWSPM).

[11]  Pär Carlshamre,et al.  Release Planning in Market-Driven Software Product Development: Provoking an Understanding , 2002, Requirements Engineering.

[12]  Tony Gorschek,et al.  The impact of agile principles on market-driven software product development , 2010, J. Softw. Maintenance Res. Pract..

[13]  D. Reinertsen.  The Principles of Product Development Flow: Second Generation Lean Product Development , 2009 .

[14]  M. Patton.  Qualitative research and evaluation methods , 1980 .

[15]  Jane Cleland-Huang,et al.  The incremental funding method: data-driven software development , 2004, IEEE Software.

[16]  R. Yin.  Case Study Research: Design and Methods , 1984 .

[17]  Ken Schwaber.  The Enterprise and Scrum , 2007 .

[18]  Slinger Jansen,et al.  A Revelatory Case Study on Scaling Agile Release Planning , 2010, 2010 36th EUROMICRO Conference on Software Engineering and Advanced Applications.

[19]  Philippe Kruchten,et al.  Using grounded theory to study the experience of software development , 2011, Empirical Software Engineering.

[20]  Helen Sharp,et al.  Motivation in Software Engineering: A systematic literature review , 2008, Inf. Softw. Technol..

[21]  Sanjiv Augustine,et al.  Managing Agile Projects , 2005 .

[22]  Alistair Cockburn,et al.  Agile Software Development , 2001 .

[23]  Hans Christian Benestad,et al.  A comparison of model-based and judgment-based release planning in incremental software projects , 2011, 2011 33rd International Conference on Software Engineering (ICSE).

[24]  Günther Ruhe,et al.  The art and science of software release planning , 2005, IEEE Software.