Welcome to the InfoSci Platform
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
Copyright: © 2019 |Pages: 22
ISBN13: 9781522563136|ISBN10: 152256313X|ISBN13 Softcover: 9781522586135|EISBN13: 9781522563143
DOI: 10.4018/978-1-5225-6313-6.ch003
Cite Chapter Cite Chapter

MLA

Rindell, Kalle, et al. "Security Assurance in Agile Software Development Methods: An Analysis of Scrum, XP, and Kanban." Exploring Security in Software Architecture and Design, edited by Michael Felderer and Riccardo Scandariato, IGI Global, 2019, pp. 47-68. https://doi.org/10.4018/978-1-5225-6313-6.ch003

APA

Rindell, K., Hyrynsalmi, S., & Leppänen, V. (2019). Security Assurance in Agile Software Development Methods: An Analysis of Scrum, XP, and Kanban. In M. Felderer & R. Scandariato (Eds.), Exploring Security in Software Architecture and Design (pp. 47-68). IGI Global. https://doi.org/10.4018/978-1-5225-6313-6.ch003

Chicago

Rindell, Kalle, Sami Hyrynsalmi, and Ville Leppänen. "Security Assurance in Agile Software Development Methods: An Analysis of Scrum, XP, and Kanban." In Exploring Security in Software Architecture and Design, edited by Michael Felderer and Riccardo Scandariato, 47-68. Hershey, PA: IGI Global, 2019. https://doi.org/10.4018/978-1-5225-6313-6.ch003

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.