Agile Manifesto
E139363
The Agile Manifesto is a foundational document in software development that outlines core values and principles favoring collaboration, adaptability, and customer-focused iterative delivery over rigid processes and extensive documentation.
All labels observed (5)
| Label | Occurrences |
|---|---|
| Agile Manifesto canonical | 11 |
| Agile software development | 1 |
| Agile software development principles | 1 |
| Manifesto for Agile Software Development | 1 |
| agile manifesto | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1224361 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
Target entity: Agile Manifesto Context triple: [Ward Cunningham, contributedTo, Agile Manifesto]
-
A.
Agile Software Development, Principles, Patterns, and Practices
"Agile Software Development, Principles, Patterns, and Practices" is a foundational software engineering book by Robert C. Martin that explains agile methodologies through object-oriented design principles, design patterns, and best practices for building maintainable code.
-
B.
Clean Code: A Handbook of Agile Software Craftsmanship
Clean Code: A Handbook of Agile Software Craftsmanship is a highly influential software engineering book by Robert C. Martin that teaches principles and practices for writing readable, maintainable, and high-quality code.
-
C.
The Pragmatic Programmer
The Pragmatic Programmer is a highly influential software development book that offers practical advice, best practices, and philosophical guidance for writing maintainable, high-quality code and growing as a professional programmer.
-
D.
The Cathedral and the Bazaar
The Cathedral and the Bazaar is a highly influential essay and book on open-source software development that contrasts centralized, top-down programming models with decentralized, collaborative approaches.
-
E.
The Mythical Man-Month
The Mythical Man-Month is a classic software engineering book by Fred Brooks that explores the challenges of large-scale software projects and famously argues that adding manpower to a late project makes it later.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: Agile Manifesto Target entity description: The Agile Manifesto is a foundational document in software development that outlines core values and principles favoring collaboration, adaptability, and customer-focused iterative delivery over rigid processes and extensive documentation.
-
A.
Agile Software Development, Principles, Patterns, and Practices
"Agile Software Development, Principles, Patterns, and Practices" is a foundational software engineering book by Robert C. Martin that explains agile methodologies through object-oriented design principles, design patterns, and best practices for building maintainable code.
-
B.
Clean Code: A Handbook of Agile Software Craftsmanship
Clean Code: A Handbook of Agile Software Craftsmanship is a highly influential software engineering book by Robert C. Martin that teaches principles and practices for writing readable, maintainable, and high-quality code.
-
C.
The Pragmatic Programmer
The Pragmatic Programmer is a highly influential software development book that offers practical advice, best practices, and philosophical guidance for writing maintainable, high-quality code and growing as a professional programmer.
-
D.
The Cathedral and the Bazaar
The Cathedral and the Bazaar is a highly influential essay and book on open-source software development that contrasts centralized, top-down programming models with decentralized, collaborative approaches.
-
E.
The Mythical Man-Month
The Mythical Man-Month is a classic software engineering book by Fred Brooks that explores the challenges of large-scale software projects and famously argues that adding manpower to a late project makes it later.
- F. None of above. chosen
Statements (70)
| Predicate | Object |
|---|---|
| instanceOf |
foundational document in agile software development
ⓘ
software development manifesto ⓘ |
| aimsTo |
enable rapid response to change
ⓘ
improve software development effectiveness ⓘ prioritize customer value ⓘ |
| author |
Alistair Cockburn
ⓘ
Andrew Hunt ⓘ Arie van Bennekum ⓘ Brian Marick ⓘ Dave Thomas ⓘ James Grenning ⓘ Jeff Sutherland ⓘ Jim Highsmith ⓘ Jon Kern ⓘ Ken Schwaber ⓘ Kent Beck ⓘ Martin Fowler ⓘ Mike Beedle ⓘ Robert C. Martin ⓘ Ron Jeffries ⓘ Steve Mellor ⓘ Ward Cunningham ⓘ |
| contrastsWith |
heavyweight software development methodologies
ⓘ
waterfall model ⓘ |
| createdIn |
Snowbird Center
ⓘ
surface form:
Snowbird, Utah, United States
|
| emphasizes |
customer collaboration over contract negotiation
ⓘ
individuals and interactions over processes and tools ⓘ responding to change over following a plan ⓘ working software over comprehensive documentation ⓘ |
| field |
project management
ⓘ
software development ⓘ software engineering ⓘ |
| focusesOn |
adaptability to change
ⓘ
agile software development ⓘ customer collaboration ⓘ incremental delivery ⓘ iterative development ⓘ lightweight processes ⓘ |
| hasComponent |
four core values
ⓘ
twelve principles ⓘ |
| hasPrinciple |
agile processes promote sustainable development
ⓘ
at regular intervals, the team reflects on how to become more effective and adjusts accordingly ⓘ build projects around motivated individuals ⓘ business people and developers must work together daily ⓘ continuous attention to technical excellence and good design enhances agility ⓘ deliver working software frequently ⓘ face-to-face conversation is the most efficient and effective method of conveying information ⓘ satisfy the customer through early and continuous delivery of valuable software ⓘ simplicity is essential ⓘ the best architectures, requirements, and designs emerge from self-organizing teams ⓘ welcome changing requirements, even late in development ⓘ working software is the primary measure of progress ⓘ |
| hasWebsite | https://agilemanifesto.org ⓘ |
| influenced |
Agile project management
ⓘ
DevOps culture ⓘ Disciplined Agile Delivery ⓘ Extreme Programming (XP) ⓘ
surface form:
Extreme Programming
Kanban (software development) ⓘ Lean software development ⓘ Scaled Agile Framework ⓘ Scrum ⓘ agile testing practices ⓘ |
| language | English ⓘ |
| numberOfSignatories | 17 ⓘ |
| publicationDate | 2001-02-11 ⓘ |
| publicationYear | 2001 ⓘ |
| relatedTo |
Agile Alliance
ⓘ
Agile Manifesto self-linksurface differs ⓘ
surface form:
Agile software development principles
|
| shortName | Agile Manifesto self-link ⓘ |
| title |
Agile Manifesto
self-linksurface differs
ⓘ
surface form:
Manifesto for Agile Software Development
|
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Subject: Agile Manifesto Description of subject: The Agile Manifesto is a foundational document in software development that outlines core values and principles favoring collaboration, adaptability, and customer-focused iterative delivery over rigid processes and extensive documentation.
Referenced by (15)
Full triples — surface form annotated when it differs from this entity's canonical label.