Agile software development
E668827
Agile software development is an iterative, collaborative approach to creating software that emphasizes flexibility, customer feedback, and continuous improvement.
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 ⓘ |
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.