The Scrum Pricing Model for Developing a Common Software Framework in a Multi-project Environment

  • Michał TurekEmail author
  • Jan Werewka
  • Dariusz Pałka
Conference paper
Part of the Advances in Intelligent Systems and Computing book series (AISC, volume 521)


The article presents a new pricing model applied in Scrum contracting. The model will introduce an innovative approach to the promotion of software products with reference to their pricing—bounding non-profit features with the classical cost estimation. It will assume a principle of single charge for all components reused in products created for different customers. The model will be applicable mainly in multi-project Scrum environments, but will also support scaled multi-team Scrum development environments (where software development work is allocated to different Scrum teams). It will introduce a complete mechanism for cost estimation, with component pricing procedures (compatible with Scrum estimation methodologies), component reuse tracking and so on. The price offered for software to be developed will depend on its popularity among customers. So, the introduction of a new feature triggered by one customer can be beneficial for all parties taking part in the framework development, with justified share of the price. In such situations a common base for software development pricing techniques must be established. It will depend on different factors, such as: team effort, team velocities, resources and technologies used. To express these values a reference currency will be defined. The model, along with pricing mechanisms presented in the article, can be effectively used in many software products in which software evolution is a core. The pricing efficiency, commonly recognized as a feature of the model, will encourage potential customers to choose a software company that uses it.


Scrum contracting Software development Agile software development Scrum Outsourcing 


  1. 1.
    Log4j—Log4j 2 Guide—Apache Log4j 2.
  2. 2.
    Maven—Welcome to Apache Maven.
  3. 3.
    Agricultural Cooperative Development. A manual for trainers. Food and Agriculture Organization of the United Nations. (1998)
  4. 4.
    The Open Group. ArchiMate 2.1 Specification. (2013)
  5. 5.
    Gradle l Modern Open-Source Enterprise Build Automation. (2015)
  6. 6.
    OMG Unified Modeling Language (OMG UML), Version 2.5 (2015)Google Scholar
  7. 7.
    Scaled Agile Framework—SAFe for Lean Software and System Engineering. (2016)
  8. 8.
  9. 9.
    Cohn, M.: Agile Estimating And Planning. Robert C. Martin Series. Prentice Hall Professional Technical Reference, Upper Saddle River (2006)Google Scholar
  10. 10.
    Derhamy, H., Eliasson, J., Delsing, J., Priller, P.: A survey of commercial frameworks for the Internet of Things. In: 2015 IEEE 20th Conference on Emerging Technologies Factory Automation (ETFA), pp. 1–8 (2015)Google Scholar
  11. 11.
    Edwin, N.M.: Software frameworks, architectural and design patterns. J. Softw. Eng. Appl. 7(8), 670–678. (2014)
  12. 12.
    Ivy, A.: The agile dependency manager. (2015)
  13. 13.
    Joshi, R., Bose, A., Scott, B.: Software Platforms for Unmanned Systems, Softwareplatform characteristics and developer advantages (2015)Google Scholar
  14. 14.
    Kaner, C., Bond, W.P.: Software Engineering Metrics: What Do They Measure and How Do We Know? (2004)Google Scholar
  15. 15.
    Küller, P., Dorsch, N., Korsakas, A.: Energy co-operatives business models: Intermediateresult from eight case studies in southern Germany. In: 2015 5th International Youth Conference on Energy (IYCE), pp. 1–8 (2015)Google Scholar
  16. 16.
    Nguyen-Cong, D., Tran-Cao, D.: A review of effort estimation studies in agile,iterative and incremental software development. In: 2013 IEEE RIVF International Conference on Computing and Communication Technologies, Research, Innovation, and Vision for the Future (RIVF), pp. 27–30 (2013)Google Scholar
  17. 17.
    Popli, R., Chauhan, N.: A sprint-point based estimation technique in Scrum. In: 2013 International Conference on Information Systems and Computer Networks (ISCON), pp. 98–103 (2013)Google Scholar
  18. 18.
    PricewaterhouseCoopers: Software Revenue Recognition A User-Friendly Guide for Navigating through the Many Complexities. (2009)
  19. 19.
    Ramasubbu, N., Balan, R.: Overcoming the challenges in cost estimation for distributed software projects. In: 2012 34th International Conference on Software Engineering (ICSE), pp. 91–101 (2012)Google Scholar
  20. 20. Normalization of story points between Scrum Teams. (2014)
  21. 21.
    Turek, M., Werewka, J.: Multi-Project Scrum Methodology for Projects Using Software Product Lines. Springer, Berlin (2016)Google Scholar
  22. 22.
    Viswanath, U., Betz, S.: Value Measurement on Performance in Global Software Development: An Industry Study on How R & D can Influence “Value for Money”. In: 2015 IEEE 10th International Conference on Global Software Engineering Workshops (ICGSEW), pp. 12–17 (2015)Google Scholar

Copyright information

© Springer International Publishing AG 2017

Authors and Affiliations

  1. 1.AGH University of Science and TechnologyKrakowPoland

Personalised recommendations