August 22, 2002
Some of the XP practices may be things we want to do all the time. Some we may wish to do only part of the time. When we are really skilled in use of a technique, we’re best equipped to decide when to use it. Here are some exercises that may help build skill. And make up your own exercises. Let us know about how they work. Added: Planning Etudes.
August 13, 2002
Using a simple deck of cards, examine how Extreme Programming gives you a new and better way of managing software.
August 2, 2002
All too often, they change the priorities and our project gets cancelled, or put on “hold”, before it’s done. This is frustrating, demoralizing, and wasteful of resources. Ship it before they can stop you! This maximizes the value of your work, and reduces stomach acid, all at the same time.
August 1, 2002
When you’re in a group that serves many customers, your backlog list tends to become infinitely long. You’re not sure whether to report on things that aren’t being done, or to pretend they are being done, or what. Don’t keep a backlog list at all. The result could be greater clarity for your customers, and far less hassle for you.
At the Agile Developer Skills course at the Raikes School, I commented that we don’t usually test accessors. But we test everything. Is this a contradiction?
Jon Bettinger has found a failing test! Excellent!
