Extreme Programming (XP) is a software development methodology intended to improve quality and responsiveness to changing requirements. It involves 5 activities - planning, managing, designing, coding, and testing. Planning includes writing user stories, release planning, and frequent small releases. Managing involves dedicated workspace, stand-up meetings, and measuring velocity. Design focuses on simplicity, metaphors, CRC cards, and refactoring. Coding uses pair programming, tests first, and integration testing. All code must have unit tests that pass before release.

1. XP ( EXTREME Programming
Model )
by : Ali masudianPour
Software Engineer Lab

2. What is XP Model ?
• Extreme Programming (XP) is a software development
methodology which is intended to improve software quality
and responsiveness to changing customer requirements.

3. Goals
• Extreme Programming Explained describes Extreme
Programming as a software development discipline that
organizes people to produce higher quality software more
productively.

4. Activity
• XP describes 5 basic activities that are performed within the
software development process:
• Planning
• Managing
• Designing
• Coding
• Testing
• Each of those activities is important.

5. Planning
• User stories are written.
• Release planning creates the release schedule.
• Make frequent small releases.
• The project is divided into repeated levels .
• repeated levels planning starts on each repeated level.

6. Managing
• Give the team a dedicated open work space.
• Set a untrack time for pace .
• A stand up meeting starts each day.
• The Project Velocity is measured.
• Move people around.
• Fix XP when it breaks.

7. Designing
• Make it simple.
• Choose a system metaphor.
• Use CRC cards for design sessions.
• Create spike solutions to reduce risk.abshar
• No functionality is added early.
• Refactor whenever and wherever possible.

8. Coding
• The customer is always available.
• Code must be written to agreed standards.
• Code the unit test first.
• All production code is pair programmed.(2 person)
• Set up a dedicated integration computer.
• Use collective codes.

9. Testing
• All code must have unit tests.
• All code must pass all unit tests before it can be released.
• When a bug is found tests are created.

10. END!
• Best regards;
• Ali MasudianPour
• References:
• http://extremeprogramming.org
• http://wikipedia.com