Manifesto for Agile Software Development

By Kent L. Beck, Michael A. Beedle, A. V. Bennekum, Alistair Cockburn, Ward Cunningham, Martin Fowler, J. Grenning, J. Highsmith, A. Hunt, Ron Jeffries and 7 more. 2013

1,554 citations recorded by the source corpus.

View Paper: https://www.semanticscholar.org/paper/3edabb96a07765704f9c6a1a5542e39ac2df640c

How researchers see this paper

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

1. Antonio Ghezzi
2. Angelo Cavallo
3. P. Li
4. Andrew Begel
5. C. Suciu
6. Roy Glen
7. J. Berbegal‐Mirabent
8. Amy J. Ko

Citations in the corpus

• What distinguishes great software engineers? (2019, methodology): “Various guidelines (notably, CMM Herbsleb et al. 1997), methods (e.g., the Spiral method Boehm 1988), and manifestos (e.g., Agile manifesto Beck et al. 2001), suggest many specific ways of working, planning, and deciding that are essential for productive teamwork.”
• A systematic literature review on agile requirements engineering practices and challenges (2015, methodology): “The Agile Manifesto states that priority should be given to ‘‘individuals and interaction over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to changes over following a plan’’ (Beck et al., 2001).”
• The Need for Design Thinking in Business Schools (2014, background): “Adaptation is facilitated by maximizing opportunities for feedback and by the creation of artifacts for inspection and development of shared understanding among team members (Beck, 2001; Leifer & Steinert, 2011; Schwaber & Sutherland, 2013).”
• Agile and adaptive governance in crisis response: Lessons from the COVID-19 pandemic (2020, unknown): “However, agile governance is related to working practices and methods to facilitate quick response (Beck et al., 2001).”
• Agile Business Model Innovation in Digital Entrepreneurship: Lean Startup Approaches (2020, background): “…and Wohlin, 2010) that value the centrality of individuals and interaction, the incremental delivery of working software, collaboration with customers and response to change (e.g. Beck et al., 2001; Senapathi and Srinivasan, 2012; Rigby et al., 2016; Cram and Newell, 2016; Paluch et al., 2017).”
• Business model innovation in entrepreneurship (2012, methodology): “The agile methodology consists of iterative and incremental developments where requirements and solutions evolve, encouraging rapid and flexible responses to change, that progressively improve the product and reduce the overall cost (Beck et al. 2001).”
• The fallacy of inscrutability (2018, methodology): “The commonly used agile paradigm [24], for example, relies on 12 core principles that prize iteration, continuous improvement, and the sustained output of ‘working’ software while also encouraging clear requirements and collaboration between stakeholders.”