programming-for-dummies

114
Software Engineering Methods
Extreme programming follows this general sequence:
1. The customer defines the program requirements.
The customer may need more features later, but initially, the customer
knows the main features he needs in a program.
2. A small team of programmers designs a simple program (a prototype)
that acts like a model for the customer to study and approve.
Because this prototype is a simple program, it’s easy to make and even
easier to modify based on the customer’s feedback and desire.
3. The programmers implement their idea as an actual program, with the
customer giving them feedback along the way.
By keeping the customer in close contact with the programmers,
extreme programming makes sure the customer can make changes to
the program while the changes are still easy to make, rather than when
the program’s finally done.
4. After the programmers create a simple program that the customer
likes, the programmers can slowly start adding additional features
that the customer may suddenly want.
In this way, a program evolves slowly with the customer guiding its development
at all times.
Extreme programming isn’t without its critics, who argue the following points:
✦ The chaotic nature of extreme programming means that it’s nearly
impossible to determine when a project gets done.
✦ The close relationship between the customer and the programmers can
be crucial.
✦ If a programmer suddenly leaves, the entire project can slow down
while the customer gets used to working with a new programmer (and
vice versa).
✦ Close communication is essential between
• The programmers and the customers
• The programmers themselves
Without constant communication, an extreme programming project can
fall apart.