Planning and feedback loops in extreme programming
Part of a series on
Software development
Core activities
Data modeling
Processes
Requirements
Design
Construction
Engineering
Testing
Debugging
Deployment
Maintenance
Paradigms and models
Agile
Cleanroom
Incremental
Prototyping
Spiral
V model
Waterfall
Methodologies and frameworks
ASD
DevOps
DAD
DSDM
FDD
IID
Kanban
Lean SD
LeSS
MDD
MSF
PSP
RAD
RUP
SAFe
Scrum
SEMAT
TDD
TSP
OpenUP
UP
XP
Supporting disciplines
Configuration management
Documentation
Software quality assurance
Project management
User experience
Practices
ATDD
BDD
CCO
CI
CD
DDD
PP
SBE
Stand-up
TDD
Tools
Compiler
Debugger
Profiler
GUI designer
UML Modeling
IDE
Build automation
Release automation
Infrastructure as code
Standards and bodies of knowledge
CMMI
IEEE standards
ISO 9001
ISO/IEC standards
PMBOK
SWEBOK
ITIL
IREB
OMG
Glossaries
Artificial intelligence
Computer science
Electrical and electronics engineering
Outlines
Outline of software development
v
t
e
Extreme programming (XP) is a software development methodology intended to improve software quality and responsiveness to changing customer requirements. As a type of agile software development,[1][2][3] it advocates frequent releases in short development cycles, intended to improve productivity and introduce checkpoints at which new customer requirements can be adopted.
Other elements of extreme programming include programming in pairs or doing extensive code review, unit testing of all code, not programming features until they are actually needed, a flat management structure, code simplicity and clarity, expecting changes in the customer's requirements as time passes and the problem is better understood, and frequent communication with the customer and among programmers.[2][3][4] The methodology takes its name from the idea that the beneficial elements of traditional software engineering practices are taken to "extreme" levels. As an example, code reviews are considered a beneficial practice; taken to the extreme, code can be reviewed continuously (i.e. the practice of pair programming).
^ abUPenn-Lectures-design-patterns "Design Patterns and Refactoring", University of Pennsylvania, 2003 Archived August 2, 2010, at the Wayback Machine.
^ abUSFCA-edu-601-lecture Extreme Programming.
^"Manifesto for Agile Software Development". Agilemanifesto.org. 2001. Retrieved March 26, 2019.
and 21 Related for: Extreme programming information
Other elements of extremeprogramming include programming in pairs or doing extensive code review, unit testing of all code, not programming features until...
methodology. Extremeprogramming has 12 practices, grouped into four areas, derived from the best practices of software engineering. Pair programming is a way...
practitioners cite inspiration from new practices at the time including extremeprogramming, scrum, dynamic systems development method, adaptive software development...
use of the phrase "mob programming" was made in ExtremeProgramming Perspectives. In addition to software coding, a mob programming team can work together...
where neither writing the program nor its use happens in an interactive way. The principle of rapid feedback in extremeprogramming is radicalized and becomes...
complex system. In procedural programming, a unit is typically a function or a module. In object-oriented programming, a unit is typically a method,...
techniques and heavy formalism. Extreme project management corresponds to extremeprogramming. Advanced approaches to extreme project management utilize the...
term used in agile software development methodologies, particularly extremeprogramming, referring to the functional testing of a user story by the software...
Kessler (2002). Pair Programming Illuminated. Boston u. a.: Addison-Wesley. ISBN 0-201-74576-3. Kent Beck (2000). ExtremeProgramming. Das Manifest (in German)...
(born 1961) is an American software engineer and the creator of extremeprogramming, a software development methodology that eschews rigid formal specification...
method, although he did not advocate integrating several times a day. Extremeprogramming (XP) adopted the concept of CI and did advocate integrating more...
sprint retrospective and sprint review meetings are timeboxed. In Extremeprogramming methodologies, development planning is timeboxed into iterations...
Beck published the first edition of the book ExtremeProgramming Explained, introducing ExtremeProgramming (XP), and the usage of user stories in the planning...
possible (a sentiment similar to that of extremeprogramming). Royce notes on the final model are: Complete program design before analysis and coding begins...
development, spiral development, rapid application development, and extremeprogramming. A life-cycle "model" is sometimes considered a more general term...
popularized the term Software Engineering Kent Beck: Refactoring, extremeprogramming, pair programming, test-driven development. Tim Berners-Lee: World Wide Web...
fraction of their time waiting for the tests to finish. Proponents of extremeprogramming and other agile software development describe this activity as an...
version (DSDM 4.2) had only contained guidance on how to use DSDM with extremeprogramming. In the early 1990s, rapid application development (RAD) was spreading...
and say that its collaboration features help because they use the extremeprogramming methodology. CPython, PyPy and IPython support, including Python...
a reaction to extreme interpretations of defensive programming, the two are not fundamentally in conflict. Rather, offensive programming adds an explicit...
Global Information