Please use this identifier to cite or link to this item:
Title: Examining perceptions of agility in software development practice
Authors: de Cesare, S
Lycett, M
Macredie, RD
Patel, C
Paul, R
Keywords: Software development;Agile practice;Software engineering;Management
Issue Date: 2010
Publisher: Association for Computing Machinery
Citation: Communications of the ACM, 53(6), 126 - 130, 2010
Abstract: Organizations undertaking software development are often reminded that successful practice depends on a number of non-technical issues that are managerial, cultural and organizational in nature. These issues cover aspects from appropriate corporate structure, through software process development and standardization to effective collaborative practice. Since the articulation of the 'software crisis' in the late-1960s, significant effort has been put into addressing problems related to the cost, time and quality of software development via the application of systematic processes and management practices for software engineering. Early efforts resulted in prescriptive structured methods, which have evolved and expanded over time to embrace consortia/ company-led initiatives such as the Unified Modeling Language and the Unified Process alongside formal process improvement frameworks such as the International Standards Organization's 9000 series, the Capability Maturity Model and SPICE. More recently, the philosophy behind traditional plan-based initiatives has been questioned by the agile movement, which seeks to emphasize the human and craft aspects of software development over and above the engineering aspects. Agile practice is strongly collaborative in its outlook, favoring individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan (see Sidebar 1). Early experience reports on the use of agile practice suggest some success in dealing with the problems of the software crisis, and suggest that plan-based and agile practice are not mutually exclusive. Indeed, flexibility may arise from this unlikely marriage in an aim to strike a balance between the rigor of traditional plan-based approaches and the need for adaptation of those to suit particular development situations. With this in mind, this article surveys the current practice in software engineering alongside perceptions of senior development managers in relation to agile practice in order to understand the principles of agility that may be practiced implicitly and their effects on plan-based approach.
Description: This is the post-print version of the final published article that is available from the link below. Copyright @ 2010 ACM.
ISSN: 0001-0782
Appears in Collections:Publications
Computer Science
Dept of Computer Science Research Papers

Files in This Item:
File Description SizeFormat 
Fulltext.pdf123.88 kBAdobe PDFView/Open
Sidebar1.pdf8.31 kBAdobe PDFView/Open
Table1.pdf67.55 kBAdobe PDFView/Open
Table2.pdf16.44 kBAdobe PDFView/Open
Table3.pdf69.06 kBAdobe PDFView/Open

Items in BURA are protected by copyright, with all rights reserved, unless otherwise indicated.