Security backlog in Scrum security practices
The rapid development of software nowadays requires the high speed software product delivery by development teams. In order to deliver the product faster, the development teams make a transformation to their conventional software development lifecycle to agile development method which can enable the...
Gespeichert in:
Hauptverfasser: | , , |
---|---|
Format: | Tagungsbericht |
Sprache: | eng |
Schlagworte: | |
Online-Zugang: | Volltext bestellen |
Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
container_end_page | 417 |
---|---|
container_issue | |
container_start_page | 414 |
container_title | |
container_volume | |
creator | Azham, Z. Ghani, I. Ithnin, N. |
description | The rapid development of software nowadays requires the high speed software product delivery by development teams. In order to deliver the product faster, the development teams make a transformation to their conventional software development lifecycle to agile development method which can enable them towards speedy delivery of software coping with the requirements-change phenomenon. In this scenario, one of the most popular techniques in Agile development is the Scrum methodology which has been criticised in term of its security aspect cycle that ignores the security risk management activity. However, the current practices suggest that security should be considered during all stages of the software development life cycle. In order to address the aforementioned issue, this paper proposes the integration of security principles in development phases using scrum and suggests the element of security backlog that can be used as security features analysis and implementation in scrum phases. |
doi_str_mv | 10.1109/MySEC.2011.6140708 |
format | Conference Proceeding |
fullrecord | <record><control><sourceid>ieee_6IE</sourceid><recordid>TN_cdi_ieee_primary_6140708</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><ieee_id>6140708</ieee_id><sourcerecordid>6140708</sourcerecordid><originalsourceid>FETCH-LOGICAL-i90t-4c22623eb45104b8027550741bf210139b87bf15ddb2904d49c06d39586d606c3</originalsourceid><addsrcrecordid>eNpVj8tqwkAYhUdKwaJ5gbrJAzTx_-c-yxJsFZQu4l4yl5Sx2spMXOTtW6hd9GwOHwc-OIQ8ItSIYJa7sV01NQXEWiIHBXpCCqM0cqEUCoZw94-BTUmR8xF-IqXRCh7IUxvcNcVhLG3nPk5f72X8LFuXrucy_y2X1LkhupDn5L7vTjkUt56R_ctq36yr7dvrpnneVtHAUHFHqaQsWC4QuNVAlRCgONqeIiAzVivbo_DeUgPcc-NAemaEll6CdGxGFr_aGEI4XFI8d2k83C6yb7maQpg</addsrcrecordid><sourcetype>Publisher</sourcetype><iscdi>true</iscdi><recordtype>conference_proceeding</recordtype></control><display><type>conference_proceeding</type><title>Security backlog in Scrum security practices</title><source>IEEE Electronic Library (IEL) Conference Proceedings</source><creator>Azham, Z. ; Ghani, I. ; Ithnin, N.</creator><creatorcontrib>Azham, Z. ; Ghani, I. ; Ithnin, N.</creatorcontrib><description>The rapid development of software nowadays requires the high speed software product delivery by development teams. In order to deliver the product faster, the development teams make a transformation to their conventional software development lifecycle to agile development method which can enable them towards speedy delivery of software coping with the requirements-change phenomenon. In this scenario, one of the most popular techniques in Agile development is the Scrum methodology which has been criticised in term of its security aspect cycle that ignores the security risk management activity. However, the current practices suggest that security should be considered during all stages of the software development life cycle. In order to address the aforementioned issue, this paper proposes the integration of security principles in development phases using scrum and suggests the element of security backlog that can be used as security features analysis and implementation in scrum phases.</description><identifier>ISBN: 9781457715303</identifier><identifier>ISBN: 1457715309</identifier><identifier>EISBN: 9781457715310</identifier><identifier>EISBN: 1457715295</identifier><identifier>EISBN: 9781457715297</identifier><identifier>EISBN: 1457715317</identifier><identifier>DOI: 10.1109/MySEC.2011.6140708</identifier><language>eng</language><publisher>IEEE</publisher><subject>Agile Development ; Blogs ; Documentation ; Programming ; Risk management ; scrum ; Security ; Software ; Testing</subject><ispartof>2011 Malaysian Conference in Software Engineering, 2011, p.414-417</ispartof><woscitedreferencessubscribed>false</woscitedreferencessubscribed></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><linktohtml>$$Uhttps://ieeexplore.ieee.org/document/6140708$$EHTML$$P50$$Gieee$$H</linktohtml><link.rule.ids>309,310,780,784,789,790,2058,27925,54920</link.rule.ids><linktorsrc>$$Uhttps://ieeexplore.ieee.org/document/6140708$$EView_record_in_IEEE$$FView_record_in_$$GIEEE</linktorsrc></links><search><creatorcontrib>Azham, Z.</creatorcontrib><creatorcontrib>Ghani, I.</creatorcontrib><creatorcontrib>Ithnin, N.</creatorcontrib><title>Security backlog in Scrum security practices</title><title>2011 Malaysian Conference in Software Engineering</title><addtitle>MySEC</addtitle><description>The rapid development of software nowadays requires the high speed software product delivery by development teams. In order to deliver the product faster, the development teams make a transformation to their conventional software development lifecycle to agile development method which can enable them towards speedy delivery of software coping with the requirements-change phenomenon. In this scenario, one of the most popular techniques in Agile development is the Scrum methodology which has been criticised in term of its security aspect cycle that ignores the security risk management activity. However, the current practices suggest that security should be considered during all stages of the software development life cycle. In order to address the aforementioned issue, this paper proposes the integration of security principles in development phases using scrum and suggests the element of security backlog that can be used as security features analysis and implementation in scrum phases.</description><subject>Agile Development</subject><subject>Blogs</subject><subject>Documentation</subject><subject>Programming</subject><subject>Risk management</subject><subject>scrum</subject><subject>Security</subject><subject>Software</subject><subject>Testing</subject><isbn>9781457715303</isbn><isbn>1457715309</isbn><isbn>9781457715310</isbn><isbn>1457715295</isbn><isbn>9781457715297</isbn><isbn>1457715317</isbn><fulltext>true</fulltext><rsrctype>conference_proceeding</rsrctype><creationdate>2011</creationdate><recordtype>conference_proceeding</recordtype><sourceid>6IE</sourceid><sourceid>RIE</sourceid><recordid>eNpVj8tqwkAYhUdKwaJ5gbrJAzTx_-c-yxJsFZQu4l4yl5Sx2spMXOTtW6hd9GwOHwc-OIQ8ItSIYJa7sV01NQXEWiIHBXpCCqM0cqEUCoZw94-BTUmR8xF-IqXRCh7IUxvcNcVhLG3nPk5f72X8LFuXrucy_y2X1LkhupDn5L7vTjkUt56R_ctq36yr7dvrpnneVtHAUHFHqaQsWC4QuNVAlRCgONqeIiAzVivbo_DeUgPcc-NAemaEll6CdGxGFr_aGEI4XFI8d2k83C6yb7maQpg</recordid><startdate>201112</startdate><enddate>201112</enddate><creator>Azham, Z.</creator><creator>Ghani, I.</creator><creator>Ithnin, N.</creator><general>IEEE</general><scope>6IE</scope><scope>6IL</scope><scope>CBEJK</scope><scope>RIE</scope><scope>RIL</scope></search><sort><creationdate>201112</creationdate><title>Security backlog in Scrum security practices</title><author>Azham, Z. ; Ghani, I. ; Ithnin, N.</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-i90t-4c22623eb45104b8027550741bf210139b87bf15ddb2904d49c06d39586d606c3</frbrgroupid><rsrctype>conference_proceedings</rsrctype><prefilter>conference_proceedings</prefilter><language>eng</language><creationdate>2011</creationdate><topic>Agile Development</topic><topic>Blogs</topic><topic>Documentation</topic><topic>Programming</topic><topic>Risk management</topic><topic>scrum</topic><topic>Security</topic><topic>Software</topic><topic>Testing</topic><toplevel>online_resources</toplevel><creatorcontrib>Azham, Z.</creatorcontrib><creatorcontrib>Ghani, I.</creatorcontrib><creatorcontrib>Ithnin, N.</creatorcontrib><collection>IEEE Electronic Library (IEL) Conference Proceedings</collection><collection>IEEE Proceedings Order Plan All Online (POP All Online) 1998-present by volume</collection><collection>IEEE Xplore All Conference Proceedings</collection><collection>IEEE/IET Electronic Library (IEL)</collection><collection>IEEE Proceedings Order Plans (POP All) 1998-Present</collection></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext_linktorsrc</fulltext></delivery><addata><au>Azham, Z.</au><au>Ghani, I.</au><au>Ithnin, N.</au><format>book</format><genre>proceeding</genre><ristype>CONF</ristype><atitle>Security backlog in Scrum security practices</atitle><btitle>2011 Malaysian Conference in Software Engineering</btitle><stitle>MySEC</stitle><date>2011-12</date><risdate>2011</risdate><spage>414</spage><epage>417</epage><pages>414-417</pages><isbn>9781457715303</isbn><isbn>1457715309</isbn><eisbn>9781457715310</eisbn><eisbn>1457715295</eisbn><eisbn>9781457715297</eisbn><eisbn>1457715317</eisbn><abstract>The rapid development of software nowadays requires the high speed software product delivery by development teams. In order to deliver the product faster, the development teams make a transformation to their conventional software development lifecycle to agile development method which can enable them towards speedy delivery of software coping with the requirements-change phenomenon. In this scenario, one of the most popular techniques in Agile development is the Scrum methodology which has been criticised in term of its security aspect cycle that ignores the security risk management activity. However, the current practices suggest that security should be considered during all stages of the software development life cycle. In order to address the aforementioned issue, this paper proposes the integration of security principles in development phases using scrum and suggests the element of security backlog that can be used as security features analysis and implementation in scrum phases.</abstract><pub>IEEE</pub><doi>10.1109/MySEC.2011.6140708</doi><tpages>4</tpages></addata></record> |
fulltext | fulltext_linktorsrc |
identifier | ISBN: 9781457715303 |
ispartof | 2011 Malaysian Conference in Software Engineering, 2011, p.414-417 |
issn | |
language | eng |
recordid | cdi_ieee_primary_6140708 |
source | IEEE Electronic Library (IEL) Conference Proceedings |
subjects | Agile Development Blogs Documentation Programming Risk management scrum Security Software Testing |
title | Security backlog in Scrum security practices |
url | https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2025-01-01T09%3A13%3A53IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-ieee_6IE&rft_val_fmt=info:ofi/fmt:kev:mtx:book&rft.genre=proceeding&rft.atitle=Security%20backlog%20in%20Scrum%20security%20practices&rft.btitle=2011%20Malaysian%20Conference%20in%20Software%20Engineering&rft.au=Azham,%20Z.&rft.date=2011-12&rft.spage=414&rft.epage=417&rft.pages=414-417&rft.isbn=9781457715303&rft.isbn_list=1457715309&rft_id=info:doi/10.1109/MySEC.2011.6140708&rft_dat=%3Cieee_6IE%3E6140708%3C/ieee_6IE%3E%3Curl%3E%3C/url%3E&rft.eisbn=9781457715310&rft.eisbn_list=1457715295&rft.eisbn_list=9781457715297&rft.eisbn_list=1457715317&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_id=info:pmid/&rft_ieee_id=6140708&rfr_iscdi=true |