Agile software development
E668827
Agile software development is an iterative, collaborative approach to creating software that emphasizes flexibility, customer feedback, and continuous improvement.
All labels observed (1)
| Label | Occurrences |
|---|---|
| Agile software development canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T7491979 — 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.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Agile software development Context triple: [software craftsmanship movement, influencedBy, Agile software development]
-
A.
Agile project management
Agile project management is an iterative, flexible approach to planning and executing work that emphasizes collaboration, customer feedback, and rapid adaptation to change.
-
B.
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.
-
C.
Lean software development
Lean software development is an agile methodology that focuses on maximizing customer value while minimizing waste through continuous improvement, fast feedback, and streamlined workflows.
-
D.
Extreme Programming Explained
Extreme Programming Explained is a foundational book by Kent Beck that introduces and details the principles, practices, and philosophy of the Extreme Programming (XP) agile software development methodology.
-
E.
Agile Manifesto
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.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Agile software development Target entity description: Agile software development is an iterative, collaborative approach to creating software that emphasizes flexibility, customer feedback, and continuous improvement.
-
A.
Agile project management
Agile project management is an iterative, flexible approach to planning and executing work that emphasizes collaboration, customer feedback, and rapid adaptation to change.
-
B.
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.
-
C.
Lean software development
Lean software development is an agile methodology that focuses on maximizing customer value while minimizing waste through continuous improvement, fast feedback, and streamlined workflows.
-
D.
Extreme Programming Explained
Extreme Programming Explained is a foundational book by Kent Beck that introduces and details the principles, practices, and philosophy of the Extreme Programming (XP) agile software development methodology.
-
E.
Agile Manifesto
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.
- F. None of above. chosen
Statements (59)
| Predicate | Object |
|---|---|
| instanceOf |
project management approach
ⓘ
software development methodology ⓘ |
| appliedIn |
IT project management
ⓘ
product development ⓘ software engineering ⓘ |
| basedOn | Agile Manifesto NERFINISHED ⓘ |
| contrastsWith | waterfall model ⓘ |
| documentedIn | Agile Manifesto for Software Development NERFINISHED ⓘ |
| emphasizes |
continuous improvement
ⓘ
customer collaboration ⓘ flexibility ⓘ incremental delivery ⓘ iterative development ⓘ responding to change ⓘ |
| goal |
enhance team productivity
ⓘ
improve software quality ⓘ increase customer satisfaction ⓘ reduce project risk ⓘ |
| hasPrinciple |
agile processes promote sustainable development
ⓘ
at regular intervals, the team reflects on how to become more effective ⓘ 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 method of communication ⓘ 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 ⓘ |
| hasValue |
customer collaboration over contract negotiation
ⓘ
individuals and interactions over processes and tools ⓘ responding to change over following a plan ⓘ working software over comprehensive documentation ⓘ |
| includesFramework |
Extreme Programming
NERFINISHED
ⓘ
Feature-Driven Development NERFINISHED ⓘ Kanban NERFINISHED ⓘ Lean software development NERFINISHED ⓘ Scrum NERFINISHED ⓘ |
| introducedIn | 2001 ⓘ |
| originatedFrom | lightweight software development methods ⓘ |
| requires |
adaptive planning
ⓘ
continuous collaboration ⓘ frequent customer feedback ⓘ |
| supports |
close collaboration with stakeholders
ⓘ
cross-functional teams ⓘ early delivery of value ⓘ frequent releases ⓘ self-organizing teams ⓘ |
| usesPractice |
backlog management
ⓘ
continuous integration ⓘ daily stand-up meetings ⓘ iterative planning ⓘ pair programming ⓘ refactoring ⓘ retrospectives ⓘ test-driven development ⓘ timeboxing ⓘ user stories ⓘ |
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.
Instruction
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.
Input
Subject: Agile software development Description of subject: Agile software development is an iterative, collaborative approach to creating software that emphasizes flexibility, customer feedback, and continuous improvement.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.