A Model for Business Value in Large-Scale Agile and Lean Software Development

  • Jeanette Heidenberg
  • Max Weijola
  • Kirsi Mikkonen
  • Ivan Porres
Part of the Communications in Computer and Information Science book series (CCIS, volume 301)


As agile and lean methods continue to increase in popularity and move away from their home ground – small, co-located teams with an actively involved customer – they are faced with new challenges. One such challenge is the definition and communication of business value in large settings, where multiple development teams interact with multiple business stakeholders. This challenge is exacerbated by the fact that the term business value in agile contexts is not clearly defined, even though the creation of business value is one of the central themes in agile and lean development. In this paper, we propose a model for business value that is intended to make explicit different factors that constitute the concept of business value in agile and lean software development. This model has been jointly developed with industrial partners in the Cloud Software Finland research project. We aim to further evaluate and develop the model in the future within this research project.


Business Value Agile Lean Feature Prioritization Large-Scale Agile 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
  2. 2.
    Ambler, S.W.: Has Agile Peaked? Dr. Dobb’s Journal: The World of Software Development 33(6), 52–54 (2008)Google Scholar
  3. 3.
    Armour, P.: When executives code. Commun. ACM 47, 19–22 (2004)CrossRefGoogle Scholar
  4. 4.
    Beck, K.: Extreme Programming Explained (2000)Google Scholar
  5. 5.
    Cloud Software Finland,
  6. 6.
    Cockburn, A.: Crystal clear a human-powered methodology for small teams. Addison-Wesley Professional (2004)Google Scholar
  7. 7.
    Cohn, M.: Agile Estimating and Planning. Prentice Hall PTR, Upper Saddle River (2005)Google Scholar
  8. 8.
    Fenton, N., Pfleeger, S.L.: Software metrics, 2nd edn. A rigorous and practical approach. PWS Publishing Co., Boston (1997)Google Scholar
  9. 9.
    Grenning, J.: Planning poker or how to avoid analysis paralysis while release planning (2002)Google Scholar
  10. 10.
    Hevner, A.R., March, S.T., Park, J., Ram, S.: Design Science in Information Systems Research. MIS Quarterly 28(1), 75–105 (2004), Google Scholar
  11. 11.
    Mediratta, B., Julie, B.: The google way: Give engineers room. The New York Times (October 2007)Google Scholar
  12. 12.
    Osterwalder, A., Pigneur, Y., Clark, T.: Business Model Generation: A Handbook for Visionaries, Game Changers, and Challengers. Wiley Desktop Editions Series. John Wiley & Sons (2010)Google Scholar
  13. 13.
    Patton, J.: Ambiguous business value harms software products. IEEE Softw. 25, 50–51 (2008)CrossRefGoogle Scholar
  14. 14.
    Pettit, R.: Business value applied: Aligning the day to day with business imperative. Agile Journal (2007)Google Scholar
  15. 15.
    Poppendieck, M., Poppendieck, T.: Implementing Lean Software Development: From Concept to Cash. Addison-Wesley Professional (2006)Google Scholar
  16. 16.
    Racheva, Z., Daneva, M., Herrmann, A., Wieringa, R.J.: A conceptual model and process for client-driven agile requirements prioritization. In: 2010 Fourth International Conference on Research Challenges in Information Science, RCIS (2010)Google Scholar
  17. 17.
    Racheva, Z., Daneva, M., Sikkel, K.: Value Creation by Agile Projects: Methodology or Mystery? In: Bomarius, F., Oivo, M., Jaring, P., Abrahamsson, P. (eds.) PROFES 2009. LNBIP, vol. 32, pp. 141–155. Springer, Heidelberg (2009)CrossRefGoogle Scholar
  18. 18.
    Racheva, Z., Daneva, M., Sikkel, K., Buglione, L.: Business Value Is Not Only Dollars – Results from Case Study Research on Agile Software Projects. In: Ali Babar, M., Vierimaa, M., Oivo, M. (eds.) PROFES 2010. LNCS, vol. 6156, pp. 131–145. Springer, Heidelberg (2010)CrossRefGoogle Scholar
  19. 19.
    Rawsthorne, D.: Managing the work in an agile project (2004),
  20. 20.
    Schwaber, K., Sutherland, J.: The scrum guide (2011),
  21. 21.
    de Ste-Croix, A., Easton, A.: The product owner team. In: Proceedings of the Agile 2008, pp. 274–279. IEEE Computer Society, Washington, DC (2008)CrossRefGoogle Scholar
  22. 22.
    Tessem, B., Maurer, F.: Job Satisfaction and Motivation in a Large Agile Team. In: Concas, G., Damiani, E., Scotto, M., Succi, G. (eds.) XP 2007. LNCS, vol. 4536, pp. 54–61. Springer, Heidelberg (2007)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2012

Authors and Affiliations

  • Jeanette Heidenberg
    • 1
    • 2
  • Max Weijola
    • 1
    • 2
  • Kirsi Mikkonen
    • 3
  • Ivan Porres
    • 1
    • 2
  1. 1.Department of Information TechnologiesÅbo Akademi UniversityTurkuFinland
  2. 2.Turku Centre for Computer ScienceTurkuFinland
  3. 3.OY L M Ericsson AbJorvasFinland

Personalised recommendations