Agile Software Development: Software Through People

1,240 citations recorded by the source corpus.

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Coevolving Systems and the Organization of Agile Software Development (2009, background): “Agility itself is defined by Highsmith and Cockburn (2001) as the “the ability to create and respond to change” (p. 120).”
Toward Agile: An Integrated Analysis of Quantitative and Qualitative Field Data (2010, background): “…pertaining to the constructs and Table 2 summarizes the key principles and practices underlying the Agile Manifesto and four commonly used agile methods that emphasize software development agility, team autonomy, and team diversity (Beck and Andres 2005; Cockburn 2001; Highsmith 2004; Larman 2004).”
Challenges and success factors for large-scale agile transformations: A systematic literature review (2016, methodology): “Traditional methods focus on up-front planning and strict management of change, but agile methods were designed to accept and eﬃciently manage change ( Highsmith and Cockburn, 2001; Cockburn and Highsmith, 2001 ).”
Empirical Findings in Agile Methods (2002, methodology): “45 & 90-person teams, described in Agile Software Development [5]”
The impact of agile practices on communication in software development (2008, background): “For example, Highsmith and Cockburn (2001) mention that informal communication between stakeholders is a significant people-factor for developers in agile software development.”