The Agile Manifesto

By Martin Fowler, Jim Highsmith. 2014

1,688 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.

Self-Organizing Roles on Agile Software Development Teams (2013, methodology): “Self-organizing teams is one of the principles behind the Agile Manifesto and have been identified as one of the critical success factors of Agile projects [9], [2], [1].”
The situational factors that affect the software development process: Towards a comprehensive reference framework (2012, methodology): “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].”
MetaGPT: Meta Programming for Multi-Agent Collaborative Framework (2023, background): “Furthermore, SOPs outline responsibilities among team members and set standards for component outputs, ensuring that tasks are executed consistently and accurately, in alignment with the defined roles and quality standards [11, 12, 13, 14].”
A systematic literature review on agile requirements engineering practices and challenges (2015, methodology): “It is the predominant method for eradicating communication gaps Collocated teams (Highsmith & Fowler, 2001) Agile principles prefers collocated teams for better communication and collaboration Onsite customer (Cao & Ramesh, 2008; Lundh & Sandberg, Pichler et al., 2006) Customer and developmentteams…”