Unit testing is very important.
Ideally, you never write a line of code that does not already have a unit test that fails. In XP, everything you write, directly fits some requirement, and is written to make some test that already exists, pass.egoless programming or collective code ownership is another feature of extreme programming. Everything is coded to a single set of standards, and anyone on the project is expected to take ownership of anything, at any time. This requires a small experienced team of peers, not a large team of craftsmen and apprentices.
~ J. McGill , University of Arizona
Extreme programming does not fear or try to control change. It attempts to make the cost of change as low as possible. Instead of rigidly following plans, it constantly adapts them.
![]() |
recommend book⇒Extreme Programming Explained: Embrace Change | ||
| paperback | kindle | ||
|---|---|---|---|
| ISBN13: | 978-0-201-61641-5 | B000OZ0N5S | |
| publisher: | Addison-Wesley | ||
| published: | 1999-10-05 | ||
| by: | Kent Beck | ||
![]() |
recommend book⇒Extreme Programming Installed | |
| paperback | ||
|---|---|---|
| ISBN13: | 978-0-201-70842-4 | |
| publisher: | Addison-Wesley | |
| published: | 2000-10-26 | |
| by: | Ron Jeffries | |
![]() |
recommend book⇒Planning Extreme Programming | |
| paperback | ||
|---|---|---|
| ISBN13: | 978-0-201-71091-5 | |
| publisher: | Addison-Wesley | |
| published: | 2000-10-26 | |
| by: | Kent Beck and Martin Fowler | |
| You can get the freshest copy of this page from: | or possibly from your local J: drive (Java virtual drive/mindprod.com website mirror) | |
| http://mindprod.com/jgloss/extremeprogramming.html | J:\mindprod\jgloss\extremeprogramming.html | |
![]() | ||
| Canadian Mind Products | ||
| mindprod.com IP:[65.110.21.43] | ||
| view Blog | Your face IP:[38.107.191.106] | |
| Feedback | You are visitor number 10,038. | |