A Paradoxical Perspective on Contradictions in Agile Software Development

An ongoing debate on agile methods focuses on the contradictions in software development, especially responding to change vs. following a plan, and people vs. processes. Unlike the 'either-or' perspective adopted in the existing agile literature, this paper introduces a paradoxical view on the contradictions in agile software development and uses two agile processes to illustrate it, arguing that a paradoxical perspective can help to gain a better understanding of the nature of and ways of dealing with the contradictions in agile software development. Taking a paradoxical perspective on responding to change vs. following a plan, and people vs. processes, this paper reveals that an agile process is a planning-driven process geared to responding to change, and it is a process that provides a supporting structure for people to learn and to improve their competences.

[1]  Barry W. Boehm,et al.  Using Risk to Balance Agile and Plan-Driven Methods , 2003, Computer.

[2]  Philip J. Streatfield,et al.  The paradox of control in organizations , 2001 .

[3]  Richard Baskerville.  Artful planning , 2006, Eur. J. Inf. Syst..

[4]  Barry W. Boehm,et al.  Agility through Discipline: A Debate , 2003, Computer.

[5]  Mark Lycett,et al.  Migrating Agile Methods to Standardized Development Practice , 2003, Computer.

[6]  K. Eisenhardt,et al.  Competing on the Edge: Strategy as Structured Chaos , 1998 .

[7]  Matt Stephens,et al.  Extreme Programming Refactored: The Case Against XP , 2003, Apress.

[8]  A. Cockburn,et al.  Agile Software Development: The People Factor , 2001, Computer.

[9]  Giancarlo Succi,et al.  Project Management and Agile Methodologies: A Survey , 2004, XP.

[10]  Jonna Kalermo,et al.  Agile software development in theory and practice , 2002 .

[11]  Richard Turner,et al.  Agile Development: Good Process or Bad Attitude? , 2002, PROFES.

[12]  Robert L. Glass.  Extreme programming: the good, the bad, and the bottom line , 2001, IEEE Software.

[13]  Pete McBreen.  Applying the Lessons of eXtreme Programming , 2000, TOOLS.

[14]  Alistair Cockburn,et al.  Agile Software Development: The Business of Innovation , 2001, Computer.

[15]  Sridhar P. Nerur,et al.  Can Agile and Traditional Systems Development Approaches Coexist? An Ambidextrous View , 2006, Inf. Syst. Manag..

[16]  C. Marlene Fiol,et al.  Capitalizing on Paradox: The Role of Language in Transforming Organizational Identities , 2002, Organ. Sci..

[17]  Dirk Riehle,et al.  A comparison of the value systems of adaptive software development and extreme programming: how methodologies may learn from each other , 2001 .

[18]  Jim Highsmith,et al.  Agile Software Development Ecosystems , 2002 .

[19]  R. Stacey.  Strategic Management and Organisational Dynamics: The Challenge of Complexity , 1999 .

[20]  R. Yin.  Case Study Research: Design and Methods , 1984 .

[21]  K. Beck,et al.  Extreme Programming Explained , 2002 .

[22]  Yvonne Dittrich,et al.  How agile are industrial software development practices? , 2006, J. Syst. Softw..

[23]  Mark C. Paulk,et al.  Extreme Programming from a CMM Perspective , 2001, IEEE Softw..

[24]  Michele Marchesi,et al.  Extreme Programming and Agile Processes in Software Engineering , 2003, Lecture Notes in Computer Science.

[25]  A. V. D. Ven,et al.  Using Paradox to Build Management and Organization Theories , 1989 .

[26]  Ken Schwaber,et al.  Agile Software Development with SCRUM , 2001 .

[27]  Barry W. Boehm,et al.  Get Ready for Agile Methods, with Care , 2002, Computer.

[28]  Gert-Jan de Vreede,et al.  Field Experiences with eXtreme Programming: Developing an Emergency Response System , 2006, J. Manag. Inf. Syst..

[29]  Richard T. Vidgen,et al.  Mapping the Information System Development Process , 2004, IT Innovation for Adaptability and Competitiveness.