A decade of agile methodologies
TL;DR: The conceptual structure underlying agile scholarship is delineated by performing an analysis of authors who have made notable contributions to the field and urging agile researchers to embrace a theory-based approach in their scholarship.
About: This article is published in Journal of Systems and Software.The article was published on 2012-06-01 and is currently open access. It has received 944 citations till now. The article focuses on the topics: Agile Unified Process & Agile usability engineering.
Citations
More filters
Proceedings Article•
01 Apr 2015TL;DR: This paper tries to investigate farthest works of the adaptation of secure engineering to agile methods, and to compile best propositions on how to conduct agile software development by still adhering security principles.
Abstract: Secure engineering is relatively more popular for software development methodologies which use standard SDLC such as waterfall, prototyping, etc. However, for agile methodologies (such as extreme programming, scrum, etc.), the adoption of secure engineering is still a debate among academics and practitioners since it potentially alter the nature of agile. This paper tries to investigate farthest works of the adaptation of secure engineering to agile methods, and to compile best propositions on how to conduct agile software development by still adhering security principles. From the review, addition/recruitment of security engineer into team is the most appreciated, while the modification of agile methodology and project management is not really favored by practitioners. This paper will be a starting point of further study to fill research/knowledge gap which is provided in this paper.
254 citations
TL;DR: This paper investigates the following research question: Which principles constitute a user-centered agile software development approach and identifies generic principles of UCASD and associating them with specific practices and processes.
Abstract: ContextIn the last decade, software development has been characterized by two major approaches: agile software development, which aims to achieve increased velocity and flexibility during the development process, and user-centered design, which places the goals and needs of the system's end-users at the center of software development in order to deliver software with appropriate usability. Hybrid development models, referred to as user-centered agile software development (UCASD) in this article, propose to combine the merits of both approaches in order to design software that is both useful and usable. ObjectiveThis paper aims to capture the current state of the art in UCASD approaches and to derive generic principles from these approaches. More specifically, we investigate the following research question: Which principles constitute a user-centered agile software development approach? MethodWe conduct a systematic review of the literature on UCASD. Identified works are analyzed using a coding scheme that differentiates four levels of UCASD: the process, practices, people/social and technology dimensions. Through subsequent synthesis, we derive generic principles of UCASD. ResultsWe identified and analyzed 83 relevant publications. The analysis resulted in a comprehensive coding system and five principles for UCASD: (1) separate product discovery and product creation, (2) iterative and incremental design and development, (3) parallel interwoven creation tracks, (4) continuous stakeholder involvement, and (5) artifact-mediated communication. ConclusionOur paper contributes to the software development body of knowledge by (1) providing a broad overview of existing works in the area of UCASD, (2) deriving an analysis framework (in form a coding system) for works in this area, going beyond former classifications, and (3) identifying generic principles of UCASD and associating them with specific practices and processes.
228 citations
TL;DR: The effect of teamwork quality on team performance, learning and work satisfaction in agile software teams, and whether this effect differs from that of traditional software teams was found to be only marginally greater for the agile teams than for the traditional teams.
216 citations
Cites methods from "A decade of agile methodologies"
...Agile development methods are used as an umbrella term to describe a number of development methods (Dingsøyr et al., 2012; Dybå and Dingsøyr, 2008)....
[...]
...Agile development methods are used as an umbrella term to describe a number of development methods ( Dingsøyr et al., 2012; Dybå and Dingsøyr, 2008 )....
[...]
TL;DR: Overall, although the topic area is very promising, it is still in its infancy, thus offering a plethora of new opportunities for both researchers and software intensive companies.
214 citations
TL;DR: A set of eight project management challenges as experienced by and as a result of self-organizing agile teams at multiple levels are identified.
181 citations
References
More filters
TL;DR: A systematic review of empirical studies of agile software development up to and including 2005 was conducted and provides a map of findings, according to topic, that can be compared for relevance to their own settings and situations.
Abstract: Agile software development represents a major departure from traditional, plan-based approaches to software engineering. A systematic review of empirical studies of agile software development up to and including 2005 was conducted. The search strategy identified 1996 studies, of which 36 were identified as empirical studies. The studies were grouped into four themes: introduction and adoption, human and social factors, perceptions on agile methods, and comparative studies. The review investigates what is currently known about the benefits and limitations of, and the strength of evidence for, agile methods. Implications for research and practice are presented. The main implication for research is a need for more and better empirical studies of agile software development within a common research agenda. For the industrial readership, the review provides a map of findings, according to topic, that can be compared for relevance to their own settings and situations.
2,399 citations
"A decade of agile methodologies" refers background in this paper
...(2005), and Dybå and Dingsøyr (2008)....
[...]
...A systematic review of empirical research published before 2005 revealed a lack of theoretical and methodological rigor (Dybå and Dingsøyr, 2008)....
[...]
...A systematic review of empirical studies published until 2005 Dybå and Dingsøyr, 2008) called for an increase in both the numer and quality of studies....
[...]
Book•
01 Oct 2001
TL;DR: Agile Software Development as discussed by the authors compares software development to a game, where team members play the game knowing that the ultimate goal is to win, always remembering what they have learned along the way, and always keeping in mind that they will never play the same way twice.
Abstract: Software development paradigms are shifting. The development group's "team" ability, and the effects of the individual developer, become more important as organizations recognize that the traditional approach of increasing process pressure and overworking team members is not getting the job done. The pioneers of Agile methodologies question the preconceived processes within which development teams work. Rather than adding to the burden of the individual developer, Agile asks "how can we change the process so that the team is more productive, while also improving quality?" The answer is in learning to play the "game." Written for developers and project managers, Agile Software Development compares software development to a game. Team members play the game knowing that the ultimate goal is to win---always remembering what they have learned along the way, and always keeping in mind that they will never play the same way twice. Players must keep an open mind to different methodologies, and focus on the goal of developing quality software in a short cycle time.
2,081 citations
TL;DR: The aim of this paper is to identify the works that have had the greatest impact on strategic management research and to analyze the changes that have taken place in the intellectual structure of this discipline.
Abstract: The aim of this paper is to identify the works that have had the greatest impact on strategic management research and to analyze the changes that have taken place in the intellectual structure of this discipline. The methodology is based on the bibliometric techniques of citation and co-citation analysis which are applied to all the articles published in the Strategic Management Journal from its first issue in 1980 through 2000. Copyright © 2004 John Wiley & Sons, Ltd.
1,274 citations
"A decade of agile methodologies" refers background in this paper
...Specifically, researchers have sed either authors (e.g., Nerur et al., 2008) or documents (e.g., amos-Rodríguez and Ruíz-Navarro, 2004) as the units of analsis....
[...]
TL;DR: The rise and fall of the dotcom-driven Internet economy shouldn't distract us from seeing that the business environment continues to change at a dramatically increasing pace, and Agile software development approaches view change from a perspective that mirrors today's turbulent business and technology environment.
Abstract: The rise and fall of the dotcom-driven Internet economy shouldn't distract us from seeing that the business environment continues to change at a dramatically increasing pace. To thrive in this turbulent environment, we must confront the business need for relentless innovation and forge the future workforce culture. Agile software development approaches, such as extreme programming, Crystal methods, lean development, Scrum, adaptive software development (ASD) and others, view change from a perspective that mirrors today's turbulent business and technology environment.
1,210 citations
TL;DR: Cocitation analysis of authors offers a new technique that might contribute to the understanding of intellectual structure in the sciences and possibly in other areas to the extent that those areas rely on serial publications.
Abstract: It is shown that the mapping of a particular area of science, in this case information science, can be done using authors as units of analysis and the cocitations of pairs of authors as the variable that indicates their “distances” from each other. The analysis assumes that the more two authors are cited together, the closer the relationship between them. The raw data are cocitation counts drawn online from Social Scisearch (Social Sciences Citation Index) over the period 1972–1979. The resulting map shows (1) identifiable author groups (akin to “schools”) of information science, (2) locations of these groups with respect to each other, (3) the degree of centrality and peripherality of authors within groups, (4) proximities of authors within group and across group boundaries (“border authors” who seem to connect various areas of research), and (5) positions of authors with respect to the map's axes, which were arbitrarily set spanning the most divergent groups in order to aid interpretation. Cocitation analysis of authors offers a new technique that might contribute to the understanding of intellectual structure in the sciences and possibly in other areas to the extent that those areas rely on serial publications. The technique establishes authors, as well as documents, as an effective unit in analyzing subject specialties.
1,104 citations