Skip to main content

Agile Tools: Toolbox for Product Owners & Agile Teams

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


Numerous digital platforms are growing at a rate of three new members per second. With such rapid growth of users, the infrastructure must be able to expand in a correspondingly agile manner. Learn about the tools you can use to design and optimize agile infrastructures. Presented in compact form: Mechanisms for agile deployment and requirement categories of an agile infrastructure. In addition to the Agile Manifesto with its 12 principles, the presentation and explanation of the Agile Onion illustrate with which values, principles, practices, processes and tools agility is related and unfolds its effect. Learn how personas assist in gaining a common understanding of users and stakeholders and their needs and behaviors by using them as actors in user stories. See a detailed persona profile illustrate the practical use of easy-to-understand persona profiles. Do you know the three essential elements of a user story? Do you know what fatal errors can be found in incorrectly or inaccurately formulated user stories? We will show you how to minimize your efforts with an optimally formulated user story and guide you to the perfect result. We explain in an easy-to-understand way the eight quality characteristics that apply to software requirements in software engineering and how you can use this knowledge to create perfect software products and digital services. We show you how to use epics in conjunction with key performance indicators to define achievable goals that delight customers. Do you know how a backlog should be organized? We present best practices of different backlog strategies that work differently and give practical recommendations on which approach works best for effective backlog usage. Are you familiar with Git repositories as indispensable tools for software development in agile teams for versioned and centralized storage of source code? The most important Git mechanisms explained compactly. We answer the question: Why is Git versioning of software so important? Use OpenAPI, another powerful tool for API design. Learn why the OpenAPI specification is the cornerstone for all-around proven open source software, behind each of which stand independent communities that further develop the respective open source projects, such as the IAM Keycloak, with new IAM releases and professional release schedules. We explain the advantages of OpenAPI interface documentation in detail. How do you succeed with pragmatic architecture documentation? How do you manage fundamental decisions regarding your software architecture documentation that are difficult to reverse over time? Are you familiar with the arc42 framework and how to achieve pragmatic software architecture documentation? Are you familiar with the quality criteria for software based on ISO/IEC 25010? Use the DevOps Periodic System to identify effective DevOps tools for your organization. Extend DevOps with BizDevOps to include the strategic component for your organization. Ensure that a content strategy and content guide is usable and lived for your organization. We show how this can be done and explain how dialog images and infographics can effectively support this. In addition, we illustrate how you can establish accompanying monitoring on the basis of suitable key performance indicators (KPI). Practical methods and tools such as timeboxing and feature-driven development explain effective strategies for achieving goals in software projects and prioritizing requirements. Complementary, Single Point Inquiry, Multi Point Inquiry and Liquid Democracy support agile prioritization.

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

USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
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


  1. Beedle, et al. Manifesto for Agile Software Development. Accessed 24 Febr 2022.

  2. Mordi, A., & Schoop, M. (2020). Making IT tangible-creating a definition of agile mindset. ECIS.

    Google Scholar 

  3. Scheller, T. (2017). Auf dem Weg zur agilen Organisation: Wie Sie Ihr Unternehmen dynamischer, flexibler und leistungsfähiger gestalten. Vahlen.

    Book  Google Scholar 

  4. Beck, K. (2000). Extreme programming explained: Embrace change. Addison-Wesley Professional.

    Google Scholar 

  5. Cohn, M. (2004). User stories applied: For agile software development. Addison-Wesley Professional.

    Google Scholar 

  6. Harbers, M., Detweiler, C., & Neerincx, M. A. (2015). Embedding stakeholder values in the requirements engineering process. In International working conference on requirements engineering: Foundation for software quality (pp. 318–332). Springer.

    Google Scholar 

  7. IEEE Standard Association, et al. (1998). IEEE recommended practice for software requirements specifications. IEEE Std-830.

    Google Scholar 

  8. Lucassen, G., et al. (2016). Improving agile requirements: The quality user story framework and tool. Requirements Engineering, 21(3), 383–403.

    Article  Google Scholar 

  9. Sedano, T., Ralph, P., & Péraire, C. (2019). The product backlog. In 2019 IEEE/ACM 41st international conference on software engineering (ICSE) (pp. 200–211). IEEE.

    Google Scholar 

  10. Lomas, C., Burke, M., & Page, C. L. (2008). Collaboration tools. Educause Learning Initiative, 2, 1–11).

    Google Scholar 

  11. Ferles, K., Stephens, J., & Dillig, I. (2020). Verifying correct usage of context-free API protocols (extended version). arXiv preprint arXiv:2010.09652.

    Google Scholar 

  12. Open API Initiative. Linux foundation. Accessed 3 Mar 2022.

  13. GitHub zur OpenAPI Spezifikation. Werkzeuge zur Anwendung der OpenAPI-Spezifikation. Accessed 3 Mar 2022.

  14. OpenApi 3.1 JSON Schema. Accessed 3 Mar 2022.

  15. OpenApi 3.1 YAML Schema. Accessed 3 Mar 2022.

  16. Hardt, D., et al. (Oktober 2012). The OAuth 2.0 authorization framework. Internet Engineering Task Force (IETF). Accessed 8 Mar 2022.

  17. Hedberg, R., et al. (September Oktober 2021). OpenID Connect Federation 1.0—draft 17. Internet Engineering Task Force (IETF). Accessed 8 Mar 2022.

  18. Sinha, Satyajit—IOT Analytics. State of IoT 2021: Number of connected IoT devices growing 9 % to 12.3 billion globally, cellular IoT now surpassing 2 billion. Accessed 8 Mar 2022.

  19. Bass, L., Clements, P., & Kazman, R. (2012). Software architecture in practice (3rd edn.). Addison-Wesley Professional.

    Google Scholar 

  20. Zörner, S. (2012). Softwarearchitekturen dokumentieren und kommunizieren (1st edn.). Carl Hanser Verlag.

    Book  Google Scholar 

  21. Cunningham, W. (1992). The WyCash portfolio management system. ACM SIGPLAN OOPS Messenger, 4(2), 29–30.

    Article  Google Scholar 

  22. Abad, Z. S. H., & Ruhe, G. (2015). Using real options to manage technical debt in requirements engineering. In 2015 IEEE 23rd international requirements engineering conference (RE) (pp. 230–235). IEEE.

    Google Scholar 

  23. Starke, G., & Hruschka, P. Das arc42 Template für Architekturentscheidungen in Softwareprojekten. Accessed 10 Mar 2022.

  24. [URL:ISO/IEC 25010:2011]. Leitfaden zur der ISO 25010 “Software product Quality Requirements and Evaluation (SQuaRE)”. Accessed 3 Mar 2022.

  25. Software Inc. Periodic table of DevOps tools. Accessed 10 Mar 2022.

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

    Article  Google Scholar 

  27. Drews, P., et al. (2017). Bimodal enterprise architecture management: The emergence of a New EAM function for a BizDevOps-based fast IT. In 2017 IEEE 21st international enterprise distributed object computing workshop (EDOCW) (pp. 57–64). IEEE.

    Google Scholar 

  28. Otto Group. Design System der Otto Group. Accessed 14 Apr 2022.

  29. Mikušová, M., & Janečková, V. (2010). Developing and implementing successful key performance indicators. World Academy of Science, Engineering and Technology, 42(6), 969–981.

    Google Scholar 

  30. Zachman, J. A. (2003). The zachman framework for enterprise architecture. Primer for enterprise engineering and manufacturing. Zachman International.

    Google Scholar 

  31. Ganesan, E., & Paturi, R. 2009. Key performance indicators framework-a method to track business objectives, link business strategy to processes and detail importance of key performance indicators in enterprise business architecture. In: Americas Conference on Information Systems. 2009.

    Google Scholar 

  32. Buschle, M., Johnson, P., & Shahzad, K. (2013). The enterprise architecture analysis tool–support for the predictive, probabilistic architecture modeling framework. In 19th Americas conference on information systems, AMCIS 2013; Chicago, IL; United States; 15 August 2013 through 17 August 2013 (pp. 3350–3364). Association for Information Systems.

    Google Scholar 

  33. Kreutzer, R. T., Neugebauer, T., & Pattloch, A. (2017). Digital Business Leadership—Digitale Transformation –Geschäftsmodell-Innovation—agile Organisation—Change-Management (1st edn.). Springer/Gabler.

    Google Scholar 

  34. FAZ vom 03.08.2015. Accessed 15 Apr 2022.

  35. Becker, J. (14. Oktober 2016). Was Audi, BMW und Daimler mit dem Kartendienst Here vorhaben. Süddeutsche Zeitung.

    Google Scholar 

  36. Bitkom—KEMPF/FRESE. Datability. Accessed 9 Mar 2014.

    Google Scholar 

  37. Leetaru, K. (17. Januar 2017). Why are we so afraid of Petabytes? Forbes Magazine.

    Google Scholar 

  38. Bitkom Research/KPMG. Mit Daten Werte schaffen. Research Studie 2015.

    Google Scholar 

  39. Hanschke, Giesinger, & Goetze. (2016). Business-Analyse—einfach und effektiv—Geschäftsanforderungen verstehen und in IT-Lösungen umsetzen (2nd edn.). Carl Hanser.

    Book  Google Scholar 

  40. Bleek, W.-G., & Wolf, H. (2011). Agile Softwareentwicklung: Werte, Konzepte und Methoden. dpunkt.

    Google Scholar 

  41. Stach, M. (2016). Agil moderieren—Konkrete Ergebnisse statt endloser Diskussion (1st edn.). Business Village.

    Google Scholar 

  42. Open-Source Software LiquidFeedback. und Accessed 10 Mar 2022.

Download references

Author information

Authors and Affiliations


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 Tools: Toolbox for Product Owners & Agile Teams. In: Large-Scale Agile Frameworks. Springer, Berlin, Heidelberg.

Download citation

  • DOI:

  • 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