eXtreme Programming

An agile software development approach that raises product quality, adapts quickly to changing customer needs, and delivers small, frequent releases through short iterations.

Key Points

  • Short iterations with small, frequent releases
  • Built-in quality using test-driven development and continuous integration
  • Collaborative engineering: pair programming and collective code ownership
  • Close customer involvement to respond rapidly to changing requirements

Example

A team building a mobile banking feature set works in one-week iterations. The customer representative is available daily to refine user stories. Developers write tests before code (TDD), pair program on critical modules, and use continuous integration to merge changes frequently. Every two weeks, the team releases a small, tested increment to production.

PMP Example Question

Which plan best reflects eXtreme Programming (XP) practices?

  1. Perform detailed design up front, freeze scope, and deliver a single release after six months.
  2. Work in 1-2 week iterations, write tests before code, pair program, and release small increments frequently.
  3. Use a strict change control board for all changes and integrate monthly to reduce merge risk.
  4. Assign modules to individual developers and avoid refactoring to maintain schedule predictability.

Correct Answer: B - Work in short iterations with TDD, pairing, and frequent small releases

Explanation: XP emphasizes high quality, rapid response to change, and frequent, small releases enabled by practices like TDD, pair programming, continuous integration, and refactoring.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Eight teaching sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Lead with clarity, influence, and outcomes.

HK School of Management and Technology offers a practical Leadership for Project Managers course for real projects, tight deadlines, and cross-functional teams. Learn to set direction, align stakeholders, and drive commitment without relying on title. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More