Agile Software Development: The Business of Innovation

By Jim Highsmith, Alistair Cockburn. Computer, 2001

1,099 citations recorded by the source corpus.

View Paper: https://www.semanticscholar.org/paper/0ee47ca8e90f3dd2107b6791c0da42357c56f5bc

How researchers see this paper

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

In Information Systems

Citations in the corpus

A Control Theory Perspective on Agile Methodology Use and Changing User Requirements (2009, methodology): “…flexible techniques, namely agile methodologies, Information Systems Research 20(3), pp. 377–399, © 2009 INFORMS that empower software development teams in the face of challenges posed by changing user requirements (Baskerville et al. 2002, Fowler and Highsmith 2001, Highsmith and Cockburn 2001).”
The situational factors that affect the software development process: Towards a comprehensive reference framework (2012, background): “However, they have been criticised for being overly mechanistic [20] and for not adequately dealing with the dynamic nature of software development – wherein requirements are often difficult to identify and finalise [21], [22].”
Can distributed software development be agile? (2006, background): “Lack of team cohesion Characteristics of Agile Development [1,4]”
New directions on agile methods: a comparative analysis (2003, background): “Agile proponents claim that the focal aspects of light and agile methods are simplicity and speed [4-6].”
Empirical Findings in Agile Methods (2002, background): “For this eWorkshop, Barry Boehm’s January 2002 IEEE Computer article [3] and the Agile Manifesto [11-13] served as background material.”
Get Ready for Agile Methods, with Care (2002, background): “” According to their world view, organizations are complex adaptive systems in which requirements are emergent rather than prespecifiable.(1) However, while agile manifesto tenets such as the second principle—welcome changing requirements, even late in development— offer great potential for success,”
A Survey on Information and Communication Technologies for Industry 4.0: State-of-the-Art, Taxonomies, Perspectives, and Challenges (2019, background): “0 (extensive automation and feedback loops): the spread of Agile approach to design and development [183], and DevOps life-”
Agile Software Development Methods: Review and Analysis (2017, background): “Highsmith and Cockburn (2001) report that the changing environment in software business also affects the software development processes itself.”
A Survey on Software-Defined Network and OpenFlow: From Concept to Implementation (2014, methodology): “The Agile SW development methodology proposed in [43] has been used to provide better feedback between different stages than conventional waterfall methodologies [44].”
Lean principles, learning, and knowledge work: Evidence from a software services provider (2011, methodology): “Within software engineering, the rise of agile methods such as Extreme Programming (XP) and Scrum have made iterative approaches possible in response to rapid changes taking place in the end-user environment (Augustine et al., 2005; Highsmith and Cockburn, 2001; Lee et al., 2006).”
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.”
Challenges of migrating to agile methodologies (2005, methodology): “They are characterized by short iterative cycles of development driven by product features, periods of reflection and introspection, collaborative decision making, incorporation of rapid feedback and change, and continuous integration of code changes into the system under development [4, 7, 8].”