Do the simplest thing, that could possibly work.

Naam M. Remmelzwaal

Bedrijf Sun Microsystems

Historie

Rol Java Consultant II

Sectie 2: Resultaten

PlanningGame: At the first monday of every week. We also did velocity measurement and saw our velocity increase week by week. Great for morale. The S curve each week was kind of a constant factor it turned out.

UnitTests: We used Junit and used HTTPUnit for XML GUI interface testing. Use the pareto principle in writing tests (80 of the volume in 20? of the time) and write a test for every bug you find! Result: a good testcoverage keeps up development speed and currage to keep modifying code when your code base grows beyond one person's comprehension.

ContinuousIntegration: In combination with Cruise Control it works like a charm for countinuous regression testing on the target platform. As a release manager one can always instantly realease!

FortyHourWeek: Keeps morale up and fatigue and errors out. We managed 40 hour weeks except for the go live week were we had to do an allnighter because of an unexpected setback and hard deadline, but we made it.

OnsiteCustomer: We had to compromise, but had a reasonably good substitute who proxied the customer for us and played his role.

CodingStandards: Followed the Java Code Conventions vigorously. Its all about cognition, implicitly recognise structures by their form/lay-out speeds up understanding of code.

Sectie 3: Ervaring

I Did my first XP project in 2001 and loved it. We had all ingredients except for an on site customer.