Skip to main content

Rapid Delivery of Software: The Effect of Alignment on Time to Market

  • Conference paper
  • First Online:
Product-Focused Software Process Improvement (PROFES 2022)

Part of the book series: Lecture Notes in Computer Science ((LNCS,volume 13709))

  • 1997 Accesses

Abstract

In Scrum, teams working collaboratively on interdependent pieces of software face alignment issues as they need to coordinate their work. Organisations aim to minimise time to market of their products, which makes it relevant to identify how alignment issues affect time to market. Currently, empirical evidence of the effect of implementing alignment activities on delivering software is scarce. This research aims to identify those alignment activities that shorten the time to market of backlog items. First, examination of key concepts led to a grounded choice of alignment activities taken into account. Use of alignment activities in development of features was identified by sending feature owners a close-ended questionnaire on the alignment of their collaborating Scrum teams. The cycle times of backlog items were measured by using the application programmable interface of the agile tool used for tracking backlog items. Results show that when user stories were developed using a shared Definition of Ready, process and lead time decreased significantly. Process and lead time also differed between user stories implementing a different number of shared feedback sessions, where using two shared feedback sessions per sprint resulted in the lowest process and lead time.

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

Access this chapter

Subscribe and save

Springer+ Basic
$34.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

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Similar content being viewed by others

Notes

  1. 1.

    https://www.scaledagileframework.com/.

  2. 2.

    less.works.

References

  1. Almeida, F.: Challenges in migration from waterfall to agile environments. World J. Comput. Appl. Technol. 5(3), 39–49 (2017)

    Article  Google Scholar 

  2. Azizyan, G., Magarian, M.K., Kajko-Matsson, M.: Survey of agile tool usage and needs. In: 2011 Agile Conference, pp. 29–38 (2011)

    Google Scholar 

  3. Bosch, J.: Speed, data, and ecosystems: the future of software engineering. IEEE Software 33(1), 82–88 (2015)

    Google Scholar 

  4. Broadcom: Rally Software. www.broadcom.com/products/software/value-stream-management/rally Accessed 19 Nov 2021

  5. Cohen, M.A., Eliasberg, J., Ho, T.-H.: New product development: the performance and time-to-market tradeoff. Manage. Sci. 42(2), 173–186 (1996)

    Article  MATH  Google Scholar 

  6. Cristal, M., Wildt, D., Prikladnicki, R.: Usage of scrum practices within a globalcompany. In: 2008 IEEE International Conference on Global Software Engineering, pp. 222–226 (2008)

    Google Scholar 

  7. Deemer, P., Benefield, G., Larman, C., Vodde, B.: The scrum primer (2010). www.brianidavidson.com/agile/docs/scrumprimer121.pdf

  8. Edison, H., Wang, X., Conboy, K.: Comparing methods for large-scale agile software development: a systematic literature review. IEEE Trans. Softw. Eng. 99, 1–1 (2021)

    Google Scholar 

  9. Hossain, E., Ali, M., Paik, H.: Using Scrum in Global Software Development: a systematic literature review. In: 2009 Fourth IEEE International Conference on Global Software Engineering, pp. 175–184 (2009)

    Google Scholar 

  10. Kim, G., Humble, J., Debois, P., Willis, J.: The DevOps handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations. IT Revolution, p. 486 (2016)

    Google Scholar 

  11. Leffingwell, D.: Mastering the iteration: an agile white paper [white paper] (2007). www.hosteddocs.ittoolbox.com/mastering-the-iteration-an-agile-white-paper.pdf

  12. Lin, J., Yu, H., Shen, Z., Miao, C.: Studying task allocation decisions of novice agile teams with data from agile project management tools. In: Proceedings of the 29th ACM/IEEE International Conference on Automated Software Engineering, pp. 689–694 (2014)

    Google Scholar 

  13. McCormick, M: Waterfall vs. agile methodology (2012). www.mccormickpcs.com/images/Waterfall vs Agile Methodology.pdf

  14. Sawyer, S., Guinan, P.: Software development: processes and performance. In: IBM Syst. J. 37(4), 552–569 (1998)

    Google Scholar 

  15. Scheerer, A., Hildenbrand, T., Kude, T.: Coordination in large-scale agile softwaredevelopment: a multiteam systems perspective. In: 2014 47th Hawaii International Conference on System Sciences, pp. 4780–4788 (2014)

    Google Scholar 

  16. Schwaber, K.: Agile project management with Scrum. Microsoft press (2004)

    Google Scholar 

  17. Sharp, H., Robinson, H.: Three ‘C’ of agile practice: collaboration, coordination and communication. In: Agile software development, pp. 61-85. Springer, Berlin (2010). https://doi.org/10.1007/978-3-642-12575-1_4

  18. Stavru, S.: A critical examination of recent industrial surveys on agile method usage. J. Syst. Softw. 94, 87–97 (2014)

    Article  Google Scholar 

  19. Kuhrmann, M., et al. (eds.): PROFES 2018. LNCS, vol. 11271. Springer, Cham (2018). https://doi.org/10.1007/978-3-030-03673-7

    Book  Google Scholar 

  20. Strode, D., Huff, S.: A Coordination perspective on agile software development, pp. 64–96 (2015)

    Google Scholar 

  21. Sürücü, C., Song, B., Krüger, J., Saake, G., Leich, T.: Establishing key performance indicators for measuring software-development processes at a large organization, pp. 1331–1341 (2020)

    Google Scholar 

  22. Szalvay, V.: An introduction to agile software development. Danube technologies, vol. 3 (2004)

    Google Scholar 

  23. Vlietland, J., van Vliet, H.: Improving it incident handling performance with information visibility. J. Softw. Evol. Process 26(12), 1106–1127 (2014)

    Article  Google Scholar 

  24. Vlietland, J., van Vliet, H.: Towards a governance framework for chains of scrum teams. Inf. Softw. Technol. 57, 52–65 (2015)

    Article  Google Scholar 

  25. Abraham, A., Gandhi, N., Hanne, T., Hong, T.-P., Nogueira Rios, T., Ding, W. (eds.): ISDA 2021. LNNS, vol. 418. Springer, Cham (2022). https://doi.org/10.1007/978-3-030-96308-8

    Book  Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Kouros Pechlivanidis .

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2022 The Author(s), under exclusive license to Springer Nature Switzerland AG

About this paper

Check for updates. Verify currency and authenticity via CrossMark

Cite this paper

Pechlivanidis, K., Wagenaar, G. (2022). Rapid Delivery of Software: The Effect of Alignment on Time to Market. In: Taibi, D., Kuhrmann, M., Mikkonen, T., Klünder, J., Abrahamsson, P. (eds) Product-Focused Software Process Improvement. PROFES 2022. Lecture Notes in Computer Science, vol 13709. Springer, Cham. https://doi.org/10.1007/978-3-031-21388-5_24

Download citation

  • DOI: https://doi.org/10.1007/978-3-031-21388-5_24

  • Published:

  • Publisher Name: Springer, Cham

  • Print ISBN: 978-3-031-21387-8

  • Online ISBN: 978-3-031-21388-5

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics