Agile Software Development Ecosystems

By J. Highsmith. 2002

930 citations recorded by the source corpus.

View Paper: https://www.semanticscholar.org/paper/8f5b8c2e470c4a2d584eb2986bf61059933063c0

How researchers see this paper

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

Citations in the corpus

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].”
Value-based software engineering: reinventing (2003, methodology): “Some agile process models such as Lean Software Development and Adaptive Software Development [19] also emphasize concurrent system and software engineering.”
Assessing and moving on from the dominant project management discourse in the light of project overruns (2005, unknown): “Highsmith [100] describes”
Empirical Findings in Agile Methods (2002, methodology): “These methodologies and practices are based on iterative enhancement, a technique which was introduced in 1975 [4] and that has been come to be known as Agile Methodologies [2, 5].”
Coevolving Systems and the Organization of Agile Software Development (2009, background): “Indeed, agile advocates claim that CAS is an appropriate theory for software development (Schwaber 1996, Highsmith 2000) and “the only way to make sense of the world” (Highsmith 2002, p. 48).”
Agile Software Development: Software Through People (2001, background): “Agile software development is a capability that can rapidly response to changing needs of the software, which focus on rapid delivery of high quality software, and achieve customer satisfaction[9].”
Agile Software Development Methods: Review and Analysis (2017, methodology): “, Highsmith 2002). In this environment, changes are expected to arrive into the project even at a very late phase. Nandhakumar and Avison (1999) found that the developers’ work practices are best characterized as having an improvisatory character where team members are protective of their profession”
A survey study of critical success factors in agile software projects (2008, unknown): “Specifically, Highsmith (2002) reports from direct experience with agile implementations, while Schatz and Abdelshafi (2005) provide results from the Primavera case study, and Karlstrom and Runeson (2005) give insight from the Star-Gate case study.”
Theoretical reflections on agile development methodologies (2007, background): “Agile approaches encourage change and question assumptions, as reflected in, for example, the “speculate-collaborate-learn” cycle of Highsmith’s Adaptive Software Development, stressing the importance of flexible/adaptive planning, extensive collaboration, and learning in achieving agility [3].”