2011
DOI: 10.1002/smr.528
|View full text |Cite
|
Sign up to set email alerts
|

Complex software project development: agile methods adoption

Abstract: The Agile Software Development paradigm has become increasingly popular in the last few years, since it claims lower costs, better productivity, better quality and better business satisfaction. Supply chain management (SCM) is a complex software development project. Owing to its scope and uncertain, complex and unstable requirements, it is not possible to develop it with predictable software development process models. Agile methodologies are targeted toward such kinds of problems that involve change and uncer… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
38
0

Year Published

2013
2013
2023
2023

Publication Types

Select...
8
1

Relationship

1
8

Authors

Journals

citations
Cited by 68 publications
(46 citation statements)
references
References 32 publications
(61 reference statements)
0
38
0
Order By: Relevance
“…2013. 213 complexity theory has been seen as an approach that allows some flexibility to deal with the main issues that impact project performance. The literature on this subject started gaining notoriety with Baccarini (1996)'s work and continued increasing with scholars that explored its application to a variety of situations and areas such as project ecologies (Newell, Goussevskaia, Swan, Bresnen, & Obembe, 2008), agile methodologies (Mishra & Mishra, 2011), problem solving (Ahern, Leavy, & Byrne, 2013), transportation projects (Owens, Ahn, Shane, Strong, & Gransberg, 2012), and knowledge sharing (Santos, Soares, & Carvalho, 2012), just to mention a few.…”
Section: Introductionmentioning
confidence: 99%
“…2013. 213 complexity theory has been seen as an approach that allows some flexibility to deal with the main issues that impact project performance. The literature on this subject started gaining notoriety with Baccarini (1996)'s work and continued increasing with scholars that explored its application to a variety of situations and areas such as project ecologies (Newell, Goussevskaia, Swan, Bresnen, & Obembe, 2008), agile methodologies (Mishra & Mishra, 2011), problem solving (Ahern, Leavy, & Byrne, 2013), transportation projects (Owens, Ahn, Shane, Strong, & Gransberg, 2012), and knowledge sharing (Santos, Soares, & Carvalho, 2012), just to mention a few.…”
Section: Introductionmentioning
confidence: 99%
“…[6] Lack of appropriate design and codes has influenced the team members to commit mistakes in higher level. [11] Schedule delay has failed to provide the improvements in the productivity, reliability and the simplicity. [16] Requirements validation, engineering issues, elicitation and specification issues are some of the requirements issues related to the agile software development.…”
Section: Discussionmentioning
confidence: 99%
“…Design flaws have created the negative impact on the organizational performance and it also has required high cost to correct the errors. Detailed dependencies have not discovered on the detailed level due to lack of design focus [11]. Agile methodologies have lack of upfront design and developing codes causes higher risk for instance and the team has engaged irrecoverable architectural mistakes due to the lack of appropriate design.…”
Section: Types Of Design and Code Changesmentioning
confidence: 99%
“…Agile exists as a range of options, from faithful "by the book" implementations to highly customized (Wang, Conboy and Cawley, 2012;Cram and Newell, 2016). A number of agile systems represent hybrids, of either agile and waterfall (Boehm, 2002), different iterations of agile methodologies (Mishra & Mishra, 2011), or of agile and software configuration management practices (Durrani, Pita & Richardson, 2013).…”
Section: The Agile Literaturementioning
confidence: 99%