The Relationship Between Scrum and Release Planning Activities: An Exploratory Case Study

  • Michail Theuns
  • Kevin Vlaanderen
  • Sjaak Brinkkemper
Part of the Management for Professionals book series (MANAGPROF)


In modern product software development settings, it becomes increasingly important to deal with rapid changes in scope, large numbers of users, and regular releases. These circumstances are ideal for an agile development method such as Scrum to prove its value. However, the implications that Scrum has on software product management (SPM) processes have not been investigated in detail. In this paper, we provide more insight into the link between release planning processes and Scrum, by performing a case study at a large Dutch social network provider. The results show an evolutionary approach to the implementation of Scrum, and the relation between several Scrum concepts and SPM capabilities. The findings presented in this paper contribute to more insight into the link between Scrum and SPM and can be of help to product software organizations that employ the Scrum development method.


Development Team Release Planning Maturity Matrice Case Company Product Owner 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


  1. Barribal, K. L., & While, A. (1994). Collecting data using a semi-structured interview: A discussion paper. Journal of Advanced Nursing, 19(2), 328–335. doi:10.1111/j.1365-2648.1994.tb01088.x.CrossRefGoogle Scholar
  2. Beck, K. (1999). Extreme programming explained: Embrace change. Boston: Addison-Wesley.Google Scholar
  3. Bekkers, W. & Spruit, M. (2010). The situational assessment method put to the test: Improvements based on case studies. Proceedings of the 4th international workshop on software product management, Sydney (pp. 7–16). doi: 10.1109/IWSPM.2010.5623871Google Scholar
  4. Bekkers, W., Spruit, M., Weerd, I. van de, Vliet, R. van, & Mahieu, A. (2010). A situational assessment method for software product management. Proceedings of the 18th European conference on information systems, Pretoria (pp. 22–34). Retrieved from
  5. Bekkers, W., van de Weerd, I., Spruit, M., & Brinkkemper, S. (2010). A framework for process improvement in software product management. In A. Riel, R. O’Connor, S. Tichkiewitch, & R. Messnarz (Eds.), Systems, software and services process improvement (pp. 1–12). Berlin/Heidelberg: Springer. doi:10.1007/978-3-642-15666-3_1.CrossRefGoogle Scholar
  6. Benbasat, I., Goldstein, D. K., & Mead, M. (1987). The case study research strategy in studies of information systems. MIS Quarterly, 11(3), 369–386. doi:10.2307/248684.CrossRefGoogle Scholar
  7. Berander, P., & Andrews, A. (2005). Requirements prioritization. In A. Aurum & C. Wohlin (Eds.), Engineering and managing software requirements (pp. 69–94). Berlin/Heidelberg: Springer.CrossRefGoogle Scholar
  8. Boehm, B., & Turner, R. (2005). Management challenges to implementing agile processes in traditional development organizations. IEEE Software, 22(5), 30–39. doi:10.1109/MS.2005.129.CrossRefGoogle Scholar
  9. Browne, G. J., & Rogich, M. B. (2001). An Empirical Investigation of User Requirements Elicitation: Comparing the Effectiveness of Prompting Techniques. Journal of Management Information Systems, 17(4), 223–249.Google Scholar
  10. Carlshamre, P. (2002). Release planning in market-driven software product development: Provoking an understanding. Requirements Engineering, 7(3), 139–151. doi:10.1007/s007660200010.CrossRefGoogle Scholar
  11. Carlshamre, P., Sandahl, K., Lindvall, M., Regnell, B., & Natt och Dag, J. (2001). An industrial survey of requirements interdependencies in software product release planning. Proceedings of the 5th IEEE international symposium on requirements engineering, Toronto (pp. 84–91). doi: 10.1109/ISRE.2001.948547Google Scholar
  12. Cooper, R. G., Edgett, S. J., & Kleinschmidt, E. J. (2001). Portfolio Management for New Product Development: Results of an Industry Practices Study. R&D Management, 31(4).Google Scholar
  13. Dingsøyr, T., Hanssen, G. K., Dybå, T., Anker, G., & Nygaard, J. O. (2006). Developing software with scrum in a small cross-organizational project. In I. Richardson, P. Runeson, & R. Messnarz (Eds.), Lecture notes in computer science (Software process improvement, Vol. 4257, pp. 5–15). Berlin/Heidelberg: Springer. doi:10.1007/11908562_2.Google Scholar
  14. Ebert, C. (2007). The impacts of software product management. Journal of Systems and Software, 80(6), 850–861. doi:10.1016/j.jss.2006.09.017.CrossRefGoogle Scholar
  15. Fitzgerald, B., Hartnett, G., & Conboy, K. (2006). Customising agile methods to software practices at Intel Shannon. European Journal of Information Systems, 15(2), 200–213. doi:10.1057/palgrave.ejis.3000605.CrossRefGoogle Scholar
  16. Hansen, M. T., & Baggesen, H. (2009). From CMMI and isolation to scrum, agile, lean and collaboration. Proceedings of the agile conference, Chicago (pp. 283–288). doi: 10.1109/AGILE.2009.18Google Scholar
  17. Jansen, S., Finkelstein, A., & Brinkkemper, S. (2009). A sense of community: A research agenda for software ecosystems. International Conference on Software Engineering (pp. 187–190). IEEE.Google Scholar
  18. Levy, Y., & Ellis, T. J. (2006). A systems approach to conduct an effective literature review in support of information systems research. Informing Science, 9(1), 181–212. Retrieved from
  19. Maglyas, A., Nikula, U., & Smolander, K. (2011). What do we know about software product management?. A systematic mapping study. Proceedings of the 5th international workshop on software product management, Trento (pp. 26–35). doi: 10.1109/IWSPM.2011.6046201Google Scholar
  20. Mann, C., & Maurer, F. (2005). A case study on the impact of Scrum on overtime and customer satisfaction. Proceedings of the agile development conference, Denver (pp. 70–79). doi: 10.1109/ADC.2005.1Google Scholar
  21. Moe, N. B., Dingsøyr, T., & Dybå, T. (2008). Understanding self-organizing teams in agile software development. Proceedings of the 19th Australian conference on software engineering, Perth (pp. 76–85). doi: 10.1109/ASWEC.2008.4483195Google Scholar
  22. Nerur, S., Mahapatra, R., & Mangalaraj, G. (2005). Challenges of migrating to agile methodologies. Communications of the ACM – Adaptive Complex Enterprises, 48(5), 72–78. doi:10.1145/1060710.1060712.Google Scholar
  23. Regnell, B., & Brinkkemper, S. (2005). Market-driven requirements engineering for software products. In A. Aurum & C. Wohlin (Eds.), Engineering and managing software requirements (pp. 287–308). Berlin/Heidelberg: Springer.CrossRefGoogle Scholar
  24. Rising, L., & Janoff, N. S. (2000). The scrum software development process for small teams. IEEE Software, 17(4), 26–32. doi:10.1109/52.854065.CrossRefGoogle Scholar
  25. Ruhe, G., & Saliu, M. O. (2005). Supporting software release planning decisions for evolving systems. Proceedings of the 29th annual IEEE/NASA software engineering workshop, Greenbelt (pp. 14–26). doi: 10.1109/SEW.2005.42Google Scholar
  26. Schwaber, K. (1995). SCRUM development process. Proceedings of the conference on object-oriented programming systems, languages, and applications, workshop on business object design and implementation (pp. 117–134).Google Scholar
  27. Sommerville, I. (2007). Software engineering (8th ed.). Boston: Addison-Wesley.Google Scholar
  28. Stapleton, J. (1997). DSDM: Dynamic systems development method. Boston: Addison-Wesley.Google Scholar
  29. Sutherland, J. (2001). Agile can scale: Inventing and reinventing scrum in five companies. Cutter IT Journal, 14(12), 5–11. Retrieved from
  30. Towill, D., & Christopher, M. (2010). The supply chain strategy conundrum: To be lean or agile or to be lean and agile? International Journal of Logistics Research and Applications, 5(3), 299–309. doi:10.1080/1367556021000026736.CrossRefGoogle Scholar
  31. Vähäniitty, J., Lassenius, C., & Rautiainen, K. (2002). An Approach to Product Roadmapping in Small Software Product Businesses. Conference Notes of the 7th European Conference on Software Quality (pp. 12–13). Helsinki: Finland.Google Scholar
  32. van de Weerd, I., & Brinkkemper, S. (2008). Meta-modeling for situation analysis and design methods. In M. R. Syed & S. N. Syed (Eds.), Handbook of research on modern systems analysis and design technologies and applications (pp. 38–58). Hershey: Idea Group Publishing.Google Scholar
  33. van de Weerd, I., Brinkkemper, S., & Versendaal, J. (2007). Concepts for incremental method evolution: Empirical exploration and validation in requirements management. In J. Krogstie, A. Opdahl, & G. Sindre (Eds.), Lecture notes in computer science (Advanced information systems engineering, Vol. 4495, pp. 469–484). Berlin/Heidelberg: Springer.Google Scholar
  34. van de Weerd, I., Brinkkemper, S., & Versendaal, S. (2010). Incremental method evolution in global software product management: A retrospective case study. Information and Software Technology, 52(7), 720–732. doi:10.1016/j.infsof.2010.03.002.CrossRefGoogle Scholar
  35. Vlaanderen, K., Weerd, I. van de, & Brinkkemper, S. (2010). Model-driven assessment in software product management. Proceedings of the 3rd international workshop on software product management, Sydney (pp. 17–25). doi: 10.1109/IWSPM.2010.5623868Google Scholar
  36. Vlaanderen, K., Jansen, S., Brinkkemper, S., & Jaspers, E. (2011). The agile requirements refinery: Applying scrum principles to software product management. Information and Software Technology, 53(1), 58–70. doi:10.1016/j.infsof.2010.08.004.CrossRefGoogle Scholar
  37. Vlaanderen, K., Weerd, I. van de, & Brinkkemper, S. (2011). The online method engine: From process assessment to method execution. Proceedings of the IFIP WG 8.1 working conference on method engineering, Paris (pp. 108–122).Google Scholar
  38. Weerd, I. van de, Brinkkemper, S., Nieuwenhuis, R., Versendaal, J., & Bijlsma, L. (2006). On the creation of a reference framework for software product management: Validation and tool support. Proceedings of the 1st international workshop on software product management, Minneapolis/St. Paul (pp. 3–12). doi: 10.1109/IWSPM.2006.6Google Scholar
  39. Weerd, I. van de, Versendaal, J., & Brinkkemper, S. (2006). A product software knowledge infrastructure for situational capability maturation: Vision and case studies in product management. Proceedings of the 12th working conference on requirements engineering: Foundation for software quality (pp. 97–112). Luxemburg: LuxemburgGoogle Scholar
  40. Yin, R. K. (2009). Case study research: Design and methods (4th ed.). London: Sage Publications.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2012

Authors and Affiliations

  • Michail Theuns
    • 1
  • Kevin Vlaanderen
    • 1
  • Sjaak Brinkkemper
    • 1
  1. 1.Department of Information and Computing SciencesUtrecht UniversityUtrechtthe Netherlands

Personalised recommendations