CSC/ECE 517 Fall 2011/ch6 6d sk: Difference between revisions
Jump to navigation
Jump to search
| Line 12: | Line 12: | ||
===Extreme Programming=== | ===Extreme Programming=== | ||
[[File:XP_SK.png|400px]]<br/> | |||
Extreme programming (XP) is currently the most popular approach to agile software development and was created by Kent Beck in 1996. XP is defined by a set of five values that establish a foundation for all work performed as part of development process. These five values are communication, simplicity, feedback, courage, and respect. Each individual value serves as a driver for specific activities, actions, and tasks. | Extreme programming (XP) is currently the most popular approach to agile software development and was created by Kent Beck in 1996. XP is defined by a set of five values that establish a foundation for all work performed as part of development process. These five values are communication, simplicity, feedback, courage, and respect. Each individual value serves as a driver for specific activities, actions, and tasks. | ||
*Communication - XP emphasize close, yet informal communication between customers and developers. This helps ensure effective communication between software engineers and other stakeholders. | *Communication - XP emphasize close, yet informal communication between customers and developers. This helps ensure effective communication between software engineers and other stakeholders. | ||
Revision as of 04:12, 15 November 2011
The Agile landscape
Overview
Introduction to Agile software development methodologies
Describe the methodologies
Extreme Programming
Extreme programming (XP) is currently the most popular approach to agile software development and was created by Kent Beck in 1996. XP is defined by a set of five values that establish a foundation for all work performed as part of development process. These five values are communication, simplicity, feedback, courage, and respect. Each individual value serves as a driver for specific activities, actions, and tasks.
- Communication - XP emphasize close, yet informal communication between customers and developers. This helps ensure effective communication between software engineers and other stakeholders.
- Simplicity - In order to achieve simplicity, XP requires developers to design only for the immediate needs of the project. This results in a simple design that can be implemented easy.
- Feedback - Feedback is received from three sources: software tests, the customer, and other software team members.
- Courage - In order to adhere to certain XP practices, Beck states that is requires courage.
- Respect - By following the other four values, an agile team will develop respect among its members and other stakeholder. As the team begins to achieve success in their delivery of software increments, they will also develop respect for the XP process itself.