Investigation on Australian Agile Software Development Organizations: An Exploratory Study of Adaptable SCM Process Implementation

2013 ◽  
Vol 8 (7) ◽  
Author(s):  
Usman K. Durrani ◽  
Joan Richardson ◽  
John Lenanrcic
Keyword(s):  
Software Development ◽  
Exploratory Study ◽  
Agile Software Development ◽  
Development Organizations ◽  
Process Implementation ◽  
Agile Software

Agile Software Development

2012 ◽  
pp. 1-15
Author(s):  
Torstein Nicolaysen ◽  
Richard Sassoon ◽  
Maria B. Line ◽  
Martin Gilje Jaatun
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Agile Development ◽  
Implementation Team ◽  
Agile Methodologies ◽  
Development Organizations ◽  
Development Lifecycle ◽  
Software Development Lifecycle ◽  
Agile Software

In this article, the authors contrast the results of a series of interviews with agile software development organizations with a case study of a distributed agile development effort, focusing on how information security is taken care of in an agile context. The interviews indicate that small and medium-sized agile software development organizations do not use any particular methodology to achieve security goals, even when their software is web-facing and potential targets of attack. This case study confirms that even in cases where security is an articulated requirement, and where security design is fed as input to the implementation team, there is no guarantee that the end result meets the security objectives. The authors contend that security must be built as an intrinsic software property and emphasize the need for security awareness throughout the whole software development lifecycle. This paper suggests two extensions to agile methodologies that may contribute to ensuring focus on security during the complete lifecycle.

scholarly journals Systematic mapping on the agility evaluation in software development organizations

2019 ◽  
Vol 16 (1) ◽  
pp. 64-76
Author(s):  
Wilson Alfredo Ortega-Ordóñez ◽  
César Jesús Pardo-Calvache ◽  
Francisco José Pino-Correa
Keyword(s):  
Software Development ◽  
Evaluation Criteria ◽  
Agile Software Development ◽  
Transformation Process ◽  
Systematic Mapping ◽  
Development Organizations ◽  
Research Stream ◽  
Agile Software ◽  
Relationship Of ◽  
The Relationship

Agile software development approaches provide great benefits for organizations; however, their implementation is subject to many challenges. For organizations is important to know the level of agility achieved and the gaps in their transformation process in order to implement improvements in their processes and take advantage of the agile approaches. Keeping this in mind, this article presents a systematic mapping of the literature about the evaluation of agility in software development organizations. As a result, 18 studies were found, which were analyzed and compared taking into account the type of study, the relationship of the evaluation with the principles and agile values, the defined evaluation criteria, the validation methods used, and the proposed tools. In addition, the factors that influence the assessment of agility and the aspects that motivate the interest in this research stream are exposed.

Threat Modeling in Agile Software Development

2022 ◽  
pp. 480-490
Author(s):  
Martin Gilje Jaatun ◽  
Karin Bernsmed ◽  
Daniela Soares Cruzes ◽  
Inger Anne Tøndel
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Risk Assessments ◽  
Limited Resources ◽  
Agile Development ◽  
Security Testing ◽  
Threat Modeling ◽  
Development Organizations ◽  
Agile Software

Threat modeling is a way to get an overview of possible attacks against your systems. The advantages of threat modeling include tackling security problems early, improved risk assessments, and more effective security testing. There will always be limited resources available for security, and threat modeling will allow you to focus on the most important areas first. There is no one single “correct” way of doing threat modeling, and “agile” is no excuse for not doing it. This chapter describes the authors' experiences with doing threat modeling with agile development organizations, outlining challenges to be faced and pitfalls to be avoided.

scholarly journals Agile Software Development

2010 ◽  
Vol 1 (3) ◽  
pp. 71-85 ◽  
Author(s):  
Torstein Nicolaysen ◽  
Richard Sassoon ◽  
Maria B. Line ◽  
Martin Gilje Jaatun
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Agile Development ◽  
Development Effort ◽  
Implementation Team ◽  
Development Organizations ◽  
Development Lifecycle ◽  
Software Development Lifecycle ◽  
Agile Software

In this article, the authors contrast the results of a series of interviews with agile software development organizations with a case study of a distributed agile development effort, focusing on how information security is taken care of in an agile context. The interviews indicate that small and medium-sized agile software development organizations do not use any particular methodology to achieve security goals, even when their software is web-facing and potential targets of attack. This case study confirms that even in cases where security is an articulated requirement, and where security design is fed as input to the implementation team, there is no guarantee that the end result meets the security objectives. The authors contend that security must be built as an intrinsic software property and emphasize the need for security awareness throughout the whole software development lifecycle. This paper suggests two extensions to agile methodologies that may contribute to ensuring focus on security during the complete lifecycle.

Sign in / Sign up

Export Citation Format

Share Document