Scribd
Upload
269 views

EXtreme Programming (XP)

eXtreme Programming (XP) is a software development methodology that defines roles, processes, and practices for teams. It focuses on rapid, flexible responses to changing requirements through short development cycles, continuous integration, simple designs, pair programming, on-site customers, and rigorous testing. The core values of XP are communication, simplicity, feedback, and courage in refactoring code. The methodology aims to balance costs, schedule, quality and scope through its planning game process.

Uploaded by

Rhea Daluddung Sanchez
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
269 views

EXtreme Programming (XP)

eXtreme Programming (XP) is a software development methodology that defines roles, processes, and practices for teams. It focuses on rapid, flexible responses to changing requirements through short development cycles, continuous integration, simple designs, pair programming, on-site customers, and rigorous testing. The core values of XP are communication, simplicity, feedback, and courage in refactoring code. The methodology aims to balance costs, schedule, quality and scope through its planning game process.

Uploaded by

Rhea Daluddung Sanchez
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 12

eXtreme

Programming (XP)

What is eXtreme Programming?

Is a software development process as well as a methodology

Defines who is doing what, when and how.

A process framework

A lightweight methodology or what Alistair Cockburn calls a


Crystal Methodology

Basic Concepts

The Four Variables


Cost
Time
Quality
Scope

The Four Values


Communication
Simplicity
Feedback
Courage

Change-driven Process
A risk is some variable that means a danger to the success of the project.
Typical risk are for instance:

Requirements change.

The users needs change.

The problem changes.

The market changes.

The requirements are imprecise or not fully understood.

Technology
Performance

The Process XP

Planning Game

Three Steps

Exploration
- The customer writes User Stories onto Index Cards.

Planning
- Commitment schedule meeting

Steering

Influencing the process by little moves

It consists of four possible move

Iteration

Recovery

New Story

Re-estimation

The Methodology XP Rules and


Practices

Management Rules and Practices

Metrics

Roles

Customer

Programmer

Coach

Tracker

Tester

Consultant

Workspace and Tools

Standup Meeting

Forty Hour Week

Development Rules and Practices


Development
Continuous
Collective

Cycle

Integration

Code Ownership

Programming

in Pairs

Coding

Standards

On-Site

Customer

Relentless

Testing

Design Rules and Practices


Do

the Simplest Thing That Could Possibly


Work (DTSTTCPW)

You

Are Not Gonna Need It (YAGIN)

Refactoring
CRC

Session (Class Responsibility Collaborator)

System
Lazy

Mercilessly

Metaphor

Optimization

You might also like