Security Assurance in Agile Software Development Methods: An Analysis of Scrum, XP, and Kanban

Security Assurance in Agile Software Development Methods: An Analysis of Scrum, XP, and Kanban

Kalle Rindell, Sami Hyrynsalmi, Ville Leppänen
ISBN13: 9781668437025|ISBN10: 1668437023|EISBN13: 9781668437032
DOI: 10.4018/978-1-6684-3702-5.ch046
Cite Chapter Cite Chapter

MLA

Rindell, Kalle, et al. "Security Assurance in Agile Software Development Methods: An Analysis of Scrum, XP, and Kanban." Research Anthology on Agile Software, Software Development, and Testing, edited by Information Resources Management Association, IGI Global, 2022, pp. 929-946. https://doi.org/10.4018/978-1-6684-3702-5.ch046

APA

Rindell, K., Hyrynsalmi, S., & Leppänen, V. (2022). Security Assurance in Agile Software Development Methods: An Analysis of Scrum, XP, and Kanban. In I. Management Association (Ed.), Research Anthology on Agile Software, Software Development, and Testing (pp. 929-946). IGI Global. https://doi.org/10.4018/978-1-6684-3702-5.ch046

Chicago

Rindell, Kalle, Sami Hyrynsalmi, and Ville Leppänen. "Security Assurance in Agile Software Development Methods: An Analysis of Scrum, XP, and Kanban." In Research Anthology on Agile Software, Software Development, and Testing, edited by Information Resources Management Association, 929-946. Hershey, PA: IGI Global, 2022. https://doi.org/10.4018/978-1-6684-3702-5.ch046

Export Reference

Mendeley
Favorite

Abstract

Agile software development was introduced in the beginning of the 2000s to increase the visibility and efficiency software projects. Since then it has become as an industry standard. However, fitting sequential security engineering development models into iterative and incremental development practices in agile methods has caused difficulties in defining, implementing, and verifying the security properties of software. In addition, agile methods have also been criticized for decreased quality of documentation, resulting in decreased security assurance necessary for regulative purposes and security measurement. As a consequence, lack of security assurance can complicate security incident management, thus increasing the software's potential lifetime cost. This chapter clarifies the requirements for software security assurance by using an evaluation framework to analyze the compatibility of established agile security development methods: XP, Scrum, and Kanban. The results show that the agile methods are not inherently incompatible with security engineering requirements.

Request Access

You do not own this content. Please login to recommend this title to your institution's librarian or purchase it from the IGI Global bookstore.