Extreme Programming (XP)

From Business Agility Library
Jump to: navigation, search
Error creating thumbnail: Unable to save thumbnail to destination

Extreme Programming (XP) is an Agile software development framework created by Kent Beck and published in 1999[1]. Like all Agile frameworks, it advocates Incremental Delivery and responding to changing Customer Requirements. XP’s focus is on the method and role of the Delivery Team, and defines four, basic activities within the software development process.

  1. Coding: The act of building a working product to the specific Customer Requirements (code is also used as a communication and problem-solving tool; by attempting to code a solution, developers can discuss complex problems and demonstrate alternative solutions).
  2. Testing: With strict emphasis on testing, especially automating testing, developers can ensure high-quality code, and the completeness of their work.
  3. Listening: Getting the developers to communicate with the Customer ensures that both parties understand the Requirements, and effort, involved in delivery.
  4. Designing: By emphasising planning and design, complex systems can be simplified, and unwanted dependencies reduced.

This is a staging page - all relevant information can be found at the authoritative website: http://www.extremeprogramming.org/

References[edit | edit source]

  1. Extreme Programming Explained: Embrace Change, Beck (1999).