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

  • Ville T. Heikkilä
  • Maria Paasivaara
  • Casper Lassenius
  • Christian Engblom
Conference paper
Part of the Lecture Notes in Business Information Processing book series (LNBIP, volume 149)


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.


release planning scrum scaling agile case study 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Schwaber, K., Beedle, M.: Agile software development with Scrum. Prentice-Hall, Upper Saddle River (2002)Google Scholar
  2. 2.
    VersionOne, Inc.: 6th Annual ”State of Agile Development” Survey (2011)Google Scholar
  3. 3.
    Cockburn, A.: Agile software development. Addison-Wesley, Boston (2002)Google Scholar
  4. 4.
    Rautiainen, K., Lassenius, C., Sulonen, R.: 4CC: A framework for managing software product development. Eng. Manag. J. 14(2), 27–32 (2002)Google Scholar
  5. 5.
    Cohn, M.: Agile estimating and planning. Prentice Hall Professional Technical Reference, Upper Saddle River (2005)Google Scholar
  6. 6.
    Leffingwell, D.: Agile software requirements: lean requirements practices for teams, programs, and the enterprise. Addison-Wesley, Upper Saddle River (2011)Google Scholar
  7. 7.
    Ruhe, G., Saliu, M.O.: The art and science of software release planning. IEEE Softw. 22(6), 47–53 (2005)CrossRefGoogle Scholar
  8. 8.
    Schwaber, K.: The enterprise and scrum. Microsoft Press, Redmond (2007)Google Scholar
  9. 9.
    Augustine, S.: Managing Agile Projects. Prentice Hall Professional Technical Reference, Upper Saddle River (2008)Google Scholar
  10. 10.
    Chow, T., Cao, D.B.: A survey study of critical success factors in agile software projects. J. Syst. Softw. 81(6), 961–971 (2008)CrossRefGoogle Scholar
  11. 11.
    Fogelström, N.D., Gorschek, T., Svahnberg, M., Olsson, P.: The impact of agile principles on market-driven software product development. J. Softw. Maint. Evol.-R. 22(1), 53–80 (2010)CrossRefGoogle Scholar
  12. 12.
    Svahnberg, M., Gorschek, T., Feldt, R., Torkar, R., Saleem, S.B., Shafique, M.U.: A systematic review on strategic release planning models. Inform. Softw. Tech. 52(3), 237–248 (2010)CrossRefGoogle Scholar
  13. 13.
    Carlshamre, P.: Release planning in market-driven software product development: Provoking an understanding. Requir. Eng. 7(3), 139–151 (2002)CrossRefGoogle Scholar
  14. 14.
    Jantunen, S., Lehtola, L., Gause, D.C., Dumdum, U.R., Barnes, R.J.: The challenge of release planning. In: Proceedings of the Fifth International Workshop on Software Product Management, pp. 36–45 (2011)Google Scholar
  15. 15.
    Benestad, H.C., Hannay, J.E.: A comparison of model-based and judgment-based release planning in incremental software projects. In: Proceeding of the 33rd International Conference on Software Engineering, pp. 766–775. ACM, New York (2011)Google Scholar
  16. 16.
    Heikkilä, V., Rautiainen, K., Jansen, S.: A revelatory case study on scaling agile release planning. In: Proceedings of the 36th Euromicro Conference on Software Engineering and Advanced Applications, pp. 289–296. IEEE Computer Society (2010)Google Scholar
  17. 17.
    Patton, M.Q.: Qualitative research and evaluation methods, 3rd edn. Sage Publications, Thousand Oaks (2002)Google Scholar
  18. 18.
    Yin, R.K.: Case study research: design and methods, 4th edn. Sage Publications, Thousand Oaks (2009)Google Scholar
  19. 19.
    Adolph, S., Hall, W., Kruchten, P.: Using grounded theory to study the experience of software development. Empir. Softw. Eng. (2011)Google Scholar
  20. 20.
    Lyon, R., Evans, M.: Scaling up pushing scrum out of its comfort zone. In: Proceedings of the Agile 2008 Conference, pp. 395–400 (2008)Google Scholar
  21. 21.
    Denne, M., Cleland-Huang, J.: The incremental funding method: Data-driven software development. IEEE Softw. 21(3), 39–47 (2004)CrossRefGoogle Scholar
  22. 22.
    Larman, C., Vodde, B.: Practices for scaling lean & agile development: large, multisite, and offshore product development with large-scale scrum. Addison-Wesley, Upper Saddle River (2010)Google Scholar
  23. 23.
    Reinertsen, D.G.: Principles of product development flow: second generation lean product development. Celeritas Publishing, Redondo Beach (2009)Google Scholar
  24. 24.
    Beecham, S., Baddoo, N., Hall, T., Robinson, H., Sharp, H.: Motivation in software engineering: A systematic literature review. Inform. Softw. Tech. 50(9-10), 860–878 (2008)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2013

Authors and Affiliations

  • Ville T. Heikkilä
    • 1
  • Maria Paasivaara
    • 1
  • Casper Lassenius
    • 1
  • Christian Engblom
    • 2
  1. 1.Department of Computer Science and EngineeringAalto UniversityHelsinkiFinland
  2. 2.Oy LM Ericsson AbKirkkonummiFinland

Personalised recommendations