scholarly journals Software Process Measurement and Related Challenges in Agile Software Development: A Multiple Case Study

2018 ◽  
pp. 272-287 ◽  
Author(s):  
Prabhat Ram ◽  
Pilar Rodriguez ◽  
Markku Oivo
Keyword(s):  
Software Development ◽  
Software Process ◽  
Multiple Case Study ◽  
Agile Software Development ◽  
Process Measurement ◽  
Multiple Case ◽  
Agile Software

scholarly journals Towards optimal quality requirement documentation in agile software development: A multiple case study

2021 ◽  
pp. 111112
Author(s):  
Woubshet Behutiye ◽  
Pilar Rodríguez ◽  
Markku Oivo ◽  
Sanja Aaramaa ◽  
Jari Partanen ◽  
...  
Keyword(s):  
Software Development ◽  
Multiple Case Study ◽  
Agile Software Development ◽  
Quality Requirement ◽  
Multiple Case ◽  
Agile Software ◽  
Optimal Quality

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.

Fixed Priced Projects in Agile

2016 ◽  
pp. 222-236
Author(s):  
Anuradha Chaminda Gajanayaka
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Development Model ◽  
Software Development Model ◽  
Responding To Change ◽  
The One ◽  
Agile Software ◽  
Development Methods ◽  
Software Development Methods

Agile software development has established as a reliable alternative to waterfall software development model. Unfortunately the use of agile software development has been limited to time based contracts and not for time limited contracts. The main reason for this limitation is the “Agile manifesto” itself. The forth value of the manifesto states that agile believers find more value in “Responding to change over following a plan”. This is the one of the main reasons why agile software development methods are not preferred for a fixed priced contract or time limited contract. The following case study provides an example on how the agile software development can be used for fixed priced software development contracts even when operating in offshore context. The agile software development concepts were used throughout to plan, execute, monitor, report, etc. for the project documented in this case study.

Sign in / Sign up

Export Citation Format

Share Document