Extreme Programming Pocket Guide

Software projects can be managed in terms of four variables (XPPG, p3):

Principle roles of people involved in a software development project:

SGB: We need to define roles we believe to be important and how each aspect of an Agile or XP process impacts each player. (See bullets on Feedback below.)

"Agree as a team - including the customer - on an acceptable level of quality. Agree to consider that time and resources are fixed. The only remaining question is that of scope. What will be delivered? When will it be delivered? The customer will set priorities for individual features. You will work on them in turn. The software will always be kept in a releasable state." XPPG, p6

Objective is to keep the level of quality constant.

Learn to estimate the amount of work you can actually do. Assume the amount will remain constant. Adjust scope to fit the project to the amount of work your team can accomplish.

Perfect is the enemy of done. Aim for a solution that is good enough.


Feedback is fundamental to every XP practice. (XPPG, pp. 8-10)

Development should be a process of refinement. We want to get to a point where this is true quickly.

Coding Practices:

Developer Practices:

Business Practices:

XP Events:

Need to spell out the benefits of XP to: