Skip to main content

Agile Prioritization Model for Software Manufacturers

  • Chapter
  • First Online:
Large-Scale Agile Frameworks
  • 574 Accesses

Abstract

In this section, a specially developed Agile organization and prioritization model for software vendors in a software product family environment is presented. This model is in principle generally valid for software manufacturers and equally usable for all organizations in which the development of software-based solutions and digital services plays a central role. It is obvious that this model will also deliver precise results in favor of your company’s success in comparable constellations. Otherwise, you can intervene at any time and adapt the agile model for your organization and needs. The decisive factor here is the democratic inclusion of all stakeholders; we have described in detail how you should proceed in this regard. The goal of the modeling of the presented Large-Scale Agile Framework is to develop an agile organization and prioritization model suitable for software manufacturers in the environment of a software product family in order to improve cross-product organization and prioritization. With adjustment to the efficient organization of software product lines the optimization, dimensions of the technical framework, the technical documentation and the interprocess communication are in the focus of such a model. For software manufacturers projects, which represent individual software products, are the actual creation of value drivers. Thus with software manufacturers the enterprise success is directly dependent on software projects, so that a detailed structured multi-project management and controlling has absolutely a high meaning. This applies in the same way to organizations whose value drivers are digital services. This includes platform operators who pursue an analog strategy. In addition to the project level, all processes that reflect the life cycle of software products must be considered for software manufacturers in particular. Pure multi-project management (MPM) does not offer suitable solutions for this. The desire for increasing flexibility also requires a departure from conventional, rigid structures. Against it the pure MPM is a strictly hierarchical organization model with typical Top down structures in pure form and is thus no up-to-date organization model for a software manufacturer.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Subscribe and save

Springer+ Basic
EUR 32.99 /Month
  • Get 10 units per month
  • Download Article/Chapter or Ebook
  • 1 Unit = 1 Article or 1 Chapter
  • Cancel anytime
Subscribe now

Buy Now

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 44.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 59.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

References

  1. Andersen, P., & Ross, J. W. (2016). Transforming the LEGO Group for the digital economy. ICIS.

    Google Scholar 

  2. Sommer, A. F. (2019). Agile transformation at LEGO Group: Implementing agile methods in multiple departments changed not only processes but also employees’ behavior and mindset. Research-Technology Management, 62(5), 20–29.

    Article  Google Scholar 

  3. LEGO YouTube Kanal. https://www.youtube.com/c/LEGO/about. Accessed 22 Febr 2022.

  4. Panke, T. alias HELD DER STEINE, YouTube Kanal. https://www.youtube.com/c/HeldderSteine/about. Accessed 22 Febr 2022.

  5. Richters, M., & Siethoff, P. Held der Steine gegen Lego – Konzern nimmt Stellung. Frankfurter Neue Presse vom 24.02.2021. https://www.fnp.de/frankfurt/held-der-steine-lego-frankfurt-youtube-streit-abmahnung-abo-fans-panke-zr-90193767.html. Accessed 22 Febr 2022.

  6. Flaschenpost, Unternehmensangaben. https://www.wirsindflaschenpost.de/. Accessed 22 Febr 2022.

  7. Ksienrzyk, L. Gründerszene. Eigentlich wollte Flaschenpost nicht verkaufen, sondern 100 Millionen einnehmen https://www.businessinsider.de/gruenderszene/food/flaschenpost-cherry-ventures-exit-r/. Accessed 22 Febr 2022.

  8. Kapalschinski, C. (15. September 2021). HANDELSBLATT. https://www.handelsblatt.com/mobilitaet/elektromobilitaet/vw-shuttle-moia-vw-will-mit-moia-das-vollautomatische-fahren-zum-weltweiten-servicegeschaeft-machen-/27614874.html. Accessed 22 Febr 2022.

  9. MOIA GmbH, Unternehmenswebsite. https://www.moia.io/de-DE/ueber-moia. Accessed 22 Febr 2022.

  10. Laukkanen, E., et al. (2018). Comparison of release engineering practices in a large mature company and a startup. Empirical Software Engineering, 2018, Jg.(Nr. 6), 1–43.

    Google Scholar 

  11. Metzger, A., & Pohl, K. (2014). Software product line engineering and variability management: Achievements and challenges. In Proceedings of the on future of software engineering (S. 70–84). ACM.

    Google Scholar 

  12. Clements, P., & Northrop, L. (2012). Software product lines: Practices and patterns (8th edn.). Addison-Wesley.

    Google Scholar 

  13. Dingsøyr, T., et al. (2018). Exploring software development at the very largescale: A revelatory case study and research agenda for agile method adaptation. Empirical Software Engineering, 23(1), 490–520.

    Article  Google Scholar 

  14. Paasivaara, M. (2017). Adopting SAFe to scale agile in a globally distributed organization. In Global Software Engineering (ICGSE), 2017 IEEE 12th international conference on (S. 36–40). IEEE.

    Google Scholar 

  15. Gustavsson, T. (2017). Assigned roles for Inter-team coordination in Large Scale agile development: A literature review. In Proceedings of the XP2017 scientific workshops (S. 15). ACM.

    Google Scholar 

  16. Baum, H.-G., et al. (2013). Strategisches Controlling (5th edn.). Schäffer-Poeschel.

    Google Scholar 

  17. Ford, D., & Ryan, C. (March–April 1981). Taking technology to market. Harvard Business Review, 2.

    Google Scholar 

  18. Goodwin, P., Meeran, S., & Dyussekeneva, K. (2014). The challenges of pre-launch forecasting of adoption time series for new durable products. International Journal of Forecasting, 30(4), 1082–1097.

    Article  Google Scholar 

  19. Fitzgerald, B., & Stol, K.-J. (2017). Continuous software engineering: A roadmap and agenda. Journal of Systems and Software, 123, 176–189.

    Article  Google Scholar 

  20. Perols, J., Zimmermann, C., & Kortmann, S. (2013). On the relationship between supplier integration and time-to-market. Journal of Operations Management, 31(3), 153–167.

    Article  Google Scholar 

  21. Starke, G., & Hruschka, P. Das arc42 Template für Architekturentscheidungen in Softwareprojekten. www.arc42.de. Accessed 23 Febr 2022.

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Sascha Block .

Rights and permissions

Reprints and permissions

Copyright information

© 2023 The Author(s), under exclusive license to Springer-Verlag GmbH, DE, part of Springer Nature

About this chapter

Check for updates. Verify currency and authenticity via CrossMark

Cite this chapter

Block, S. (2023). Agile Prioritization Model for Software Manufacturers. In: Large-Scale Agile Frameworks. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-662-67782-7_5

Download citation

  • DOI: https://doi.org/10.1007/978-3-662-67782-7_5

  • Published:

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-662-67781-0

  • Online ISBN: 978-3-662-67782-7

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics