Extreme Programming (XP)


Extreme programming (XP) is an agile software development framework noted for its heavy emphasis on software engineering practices.

  • takes good software development practices to extreme levels and codifies them
  • aims to create a higher quality of life for the developer and better software for the customer
  • believes in the 40-hour workweek alongside frequent releases and customer centricity
  • uses lean thinking to improve
  • emphasis on simplicity

5 Values

  • Communication
  • Simplicity
  • Feedback
  • Respect
  • Courage

Roles

  1. Customer
    • decides which features are needed eventually and which are needed next
  2. Tracker
    • captures metrics, measures progress, and looks for improvement opportunities
    • usually a part-time role
  3. Coach
    • mentors team members on how to use XP practices
    • usually somebody outside the team who has experience in XP

Common XP Practices

  • XP framework is built to be modified

    • teams can choose which practices to adopt
  • Pair programming

    • two software engineers work side by side to create code at once
    • typically, one person writes code, while the second person watches and provides feedback
  • Ten-minute build

    • it should take ten minutes or less to build, test, and deploy the entire system
    • If it takes longer, developers are less likely to run the tests.
    • drives other good practices, such as writing clean tests and automating testing and integrations
  • Continuous integration

    • merge local code onto the main repository regularly
    • Frequent integration reduces conflicts and allows automatic builds and tests to run
  • Test-first programming

    • aka Test Driven Development (TDD)
    • writes tests and then writes the code to pass the tests
    • developers write just enough code to pass the test, then move on to the next work item
  • Incremental design

    • Small, frequent improvements are more valuable than delayed releases
  • Sit together

    • teams often work in a shared, open space
  • Whole team

    • everybody needed for a project is on the team
  • On-Site Customer

    • XP includes the customer on the team
    • collocated with the team whenever feasible
  • Energized work

    • XP believes people are at their best when they aren’t exhausted
    • Employees should work no more than 40 hours
    • If somebody has to work overtime one week, they cannot do so the following week
  • Stories

    • aka user stories
    • are the customer requirements or features
    • user’s needs are written in a short, descriptive format that conveys what the user wants and how it would help them
  • Weekly cycle

    • heartbeat or pulse of the team, similar to a sprint cadence
    • Each week, the team selects stories and plans work for the week
  • Quarterly cycle

    • a planning and reflection event
    • team inspects and adapts their processes
      • similar to Scrum’s retrospective
    • identify the major themes for the project and create stories to deliver on them
      • themes serve the same purpose as Scrum’s product goal
  • Slack

    • a team’s weekly plan should not be filled to capacity with nonnegotiable, high-priority work
      • creates too much pressure and takes away flexibility
    • build slack into the team’s weekly plan by
      • including optional tasks that the team can reschedule if they don’t have time to complete them

Strengths

  • highly efficient
  • builds the most essential increments first
  • does not waste time on low-priority features
  • Continuous integration, automation, and a high rate of adaptability are built into the process out of necessity
  • team-focused practices
  • experience less project failure because the customer is a team member

Weaknesses

  • limited use outside software development
  • rapid pace of the work can cause high levels of stress on the developers
  • minimal documentation can hinder new team members’ understanding
  • relies on face-to-face interaction between team members and customers

Use Cases

  • best for:
    • Small, collocated teams who must manage changing and unknown requirements
    • Projects with tight deadlines
    • Teams with test automation capabilities

D322

Systems are developed by a team of fewer than a dozen individuals working in a communal workspace, where they freely share ideas and assist each other in the development project.

  • system is developed incrementally by repeated daily cycles
  • informal processes
  • regular system updates