Extreme Programming (XP)

When making an issue takes far more time than just doing the work itself. WIP.

TODO: Add lucide icons to mindmap

Introduction

What's Extreme Programming (XP)?

  • A set of rigorous software development practices built on top of the Agile methodology.
  • Rapid release cadence over tiny development cycles.
  • Emphasizes Test-Driven Development (TDD), Pair Programming, Continuous Integration, and Collective Code Ownership.

Core Principles

TODO: Add color schema to mindmap

Key Practices

Essential principles followed in extreme programming.


  • Pair Programming

    Two developers work together at one workstation at the same time, boosting velocity.

  • Test-Driven Development (TDD)

    Write tests before implementing features, ensuring code meets requirements and maintains high test coverage.

  • Small Releases

    Release working software frequently, often in small increments, to get feedback and improve based on user needs.

  • Refactoring

    Regularly improve and optimize code without changing its functionality.

  • Sustainable Pace

    Avoid overworking the team to maintain a consistent and sustainable workflow.

  • Collective Code Ownership

    Everyone on the team is responsible for all the code. Encourage collaboration and reduces silos.

  • On-Site User

    Have users readily available to clarify requirements and provide immediate feedback

Feedback loop

TODO: Check color schema for diagram below

Extreme Programming - Wikipedia.

On this page

Made with 💚 for Hackers by HackersSponsored by
Netlify Logo