extreme programming Comparison Table

Object Oriented Software Engineering View all facts Glossary Help

subject > methodology > extreme programming

Next methodology: Rational Unified Process Up: methodology, process model

extreme programming comparison table

Subject describe have web site require function as help has definition be be often supported by is a subtopic of is a synonym of is a kind of promote is an instance of have principles have philosophy

methodology aspects of project management the use of a particular notation and the production of documentation in particular formats A description of a process; it usually prescribes how to do things in a step by step manner tools developed by the author of the process, or others 5.1 - What is UML? subject

process model an aid to thinking, not as a rigid prescription of the way to do things the project manager and his or her team to decide what work should be done and in what sequence to perform the work A general approach for organizing a project into activities; an aid to thinking, not a rigid prescription of the way to do things 11.2 - Software Process Models software process model subject

extreme programming aspects of project management www.extremeprogramming.org the use of a particular notation and the production of documentation in particular formats an aid to thinking, not as a rigid prescription of the way to do things the project manager and his or her team to decide what work should be done and in what sequence to perform the work A process model and methodology that provides a disciplined approach to highly incremental and user-centred development of small projects popular for small projects that involve uncertain, changing requirements and other sources of high risk tools developed by the author of the process, or others 11.2 - Software Process Models the use of CRC cards, a focus on simplicity, creation of 'spike' throwaway prototypes when difficult technical issues are encountered, merciless restructuring of code, frequent integration, programming in pairs, and continual improvement process model
The development team includes all the stakeholders
Large requirements documents are replaced by short user stories which dictate project planning
Releases are small and frequent
Planning takes place just before the start of each iteration
Scope, resources and time are the three project variables that can be changed. Management can only dictate two of these; the developers determine the third
Quality should not be sacrificed
In order to ensure high quality, design for testability is emphasized: Automated test cases are written before the software is developed
software developers should not need to be overworked, so overtime should not be needed

Subject	describe	have web site	require	function as	help	has definition	be	be often supported by	is a subtopic of	is a synonym of	is a kind of	promote	is an instance of	have principles	have philosophy
methodology	aspects of project management		the use of a particular notation and the production of documentation in particular formats			A description of a process; it usually prescribes how to do things in a step by step manner		tools developed by the author of the process, or others	5.1 - What is UML?		subject
process model				an aid to thinking, not as a rigid prescription of the way to do things	the project manager and his or her team to decide what work should be done and in what sequence to perform the work	A general approach for organizing a project into activities; an aid to thinking, not a rigid prescription of the way to do things			11.2 - Software Process Models	software process model	subject
extreme programming	aspects of project management	www.extremeprogramming.org	the use of a particular notation and the production of documentation in particular formats	an aid to thinking, not as a rigid prescription of the way to do things	the project manager and his or her team to decide what work should be done and in what sequence to perform the work	A process model and methodology that provides a disciplined approach to highly incremental and user-centred development of small projects	popular for small projects that involve uncertain, changing requirements and other sources of high risk	tools developed by the author of the process, or others	11.2 - Software Process Models			the use of CRC cards, a focus on simplicity, creation of 'spike' throwaway prototypes when difficult technical issues are encountered, merciless restructuring of code, frequent integration, programming in pairs, and continual improvement	process model	The development team includes all the stakeholders Large requirements documents are replaced by short user stories which dictate project planning Releases are small and frequent Planning takes place just before the start of each iteration Scope, resources and time are the three project variables that can be changed. Management can only dictate two of these; the developers determine the third Quality should not be sacrificed In order to ensure high quality, design for testability is emphasized: Automated test cases are written before the software is developed	software developers should not need to be overworked, so overtime should not be needed

Next methodology: Rational Unified Process Up: methodology, process model