Ensuring Compliance with Sprint Requirements in SCRUM

Preventive Quality Assurance in SCRUM
  • Manuel PastranaEmail author
  • Hugo Ordóñez
  • Ana Rojas
  • Armando Ordoñez
Conference paper
Part of the Advances in Intelligent Systems and Computing book series (AISC, volume 924)


Compliance with the client requirements is a key factor for the success of projects. However, this compliance is not always easy to monitor and verify. SCRUM framework flexibility makes it possible to include a variety of techniques and good practices from other methods to help software development teams to achieve their goals. Some of these tools can track historical changes in the code (versioning), perform code inspection to identify bugs, vulnerabilities, code duplication, and code smells that can affect the software quality. This paper presents a preventive software quality assurance environment that aims at improving the quality of the development process.


SCRUM Software development process Software quality assurance Agile development process 


  1. 1.
    Hastie, S., Wojewoda, S.: Standish Group 2015 Chaos Report - Q&A with Jennifer Lynch., 2015. [Online]. Available:
  2. 2.
    Pressman, R.S., Ph, D.: Ingeniería del SoftwareGoogle Scholar
  3. 3.
    Pastrana, M., Ordóñez, H., Ordonez, A., Thom, L.H., Merchan, L.: Optimization of the inception deck technique for eliciting requirements in SCRUM through business process models. In: International Conference on Business Process Management, vol. 4928, no. January, pp. 649–655 (2018)Google Scholar
  4. 4.
    Kruchten, P.: Planos Arquitectónicos: El Modelo de ‘4 + 1’ Vistas de la La Arquitectura del Software. IEEE Softw. 12(6), 1–16 (2006)Google Scholar
  5. 5.
    Pressman, R.S.: Software Engineering A Practitioner’s Approach, vol. 33, p. 930. McGraw-Hill (2010)Google Scholar
  6. 6.
    Sommerville, I.: Ingeniera del Software. Septima (2005)Google Scholar
  7. 7.
    Larman, C., Vodde, B.: Scaling Agile Development—Large and Multisite Product Development with Large-Scale Scrum. CrossTalk, no. May–June, pp. 8–12 (2013)Google Scholar
  8. 8.
    Larman, C.: Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (2004)Google Scholar
  9. 9.
    Fowler, M., Highsmith, J.: The agile manifesto. Softw. Dev. 9, 28–35 (2001)Google Scholar
  10. 10.
    Schwaber, K., Sutherland, J.: La Guía de Scrum TM La Guía Definitiva de Scrum: Las Reglas del Juego, pp. 1–21 (2017)Google Scholar
  11. 11.
    I. SCRUMstudyTM, una marca de VMEdu: A Guide to the SCRUM Body of Knowledge (SBOKTMGUIDE) 2016 Edition, 2016th ed. Phoenix, Arizona 85008 USA: SCRUMstudyTM, una marca de VMEdu, Inc. (2016)Google Scholar
  12. 12.
    Kniberg, H.: Scrum and XP desde las trincheras (2007)Google Scholar
  13. 13.
    IEEE 1998, “IEEE Std 830-1998”: Especificación Requisitos Softw. según el estándar IEEE 830, p. 19 (2000)Google Scholar
  14. 14.
    Beck, K.: Extreme Programming Explained: Embrace Change, no. c. 1999Google Scholar
  15. 15.
    Cohn, M.: User Stories Applied: For Agile Software Development. Addison Wesley Signature Series, vol. 1, no. 0 (2004)Google Scholar
  16. 16.
    Hommel, S., Microsystems, S., Molpeceres, A.: Java TM (2001)Google Scholar
  17. 17.
    Hanssen, G.K., Haugset, B., Stålhane, T., Myklebust, T., Kulbrandstad, I.: Quality assurance in scrum applied to safety critical software. Lecture Notes in Business Information Processing, vol. 251, pp. 92–103 (2016)CrossRefGoogle Scholar
  18. 18.
    Pressman, R.S.: Software Engineering A Practitioner’s Approach, 7th edn. In: Pressman, R.S. (2009)Google Scholar
  19. 19.
    Deshpande, A., Riehle, D.: Continuous integration in open source software development. Open Source Dev. Communities Qual. 275, 273–280 (2008)Google Scholar
  20. 20.
    Humble, J., Farley, D.: Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation (2010)Google Scholar

Copyright information

© Springer Nature Singapore Pte Ltd. 2019

Authors and Affiliations

  • Manuel Pastrana
    • 1
    Email author
  • Hugo Ordóñez
    • 2
  • Ana Rojas
    • 1
  • Armando Ordoñez
    • 3
  1. 1.GrintTic, Universidad Antonio José CamachoCaliColombia
  2. 2.Research Laboratory in Development of Software EngineeringUniversidad San BuenaventuraCaliColombia
  3. 3.Intelligent Management Systems, University Foundation of PopayanPopayánColombia

Personalised recommendations