Forty-Hour Week
One time on the authors' C3 project, the entire team went into a heavy overtime mode in order to meet some delivery date. (Yes, even Extreme teams can get up against a deadline once in a while. Scope had not been managed properly, and we were up against it.) We worked really hard for a few weeks. Most of the team were coming in on weekends, in the middle of the night, and generally acting like we were in Silicon Valley instead of Michigan.
After the crunch was over, we all took some time off and then got back to it. We looked upon the work we had done in the overtime period, and unlike the Creator, we did not see that it was good. In fact, it was bad.[1] We found poorly written code, we found untested code, and we found unrefactored ...
Get Extreme Programming Installed now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
