Energized Work

Energized Work is the XP practice of working only as many hours as you can be productive, and only as many as you can sustain week after week.

The 1999 edition called it the 40-Hour Week, and the rename is an improvement rather than a euphemism. Forty is a number, and a number invites the argument about whether it is the right one, which is not the argument that matters. What matters is the claim underneath: hours spent tired are not merely worth less, they can be worth less than zero, because a defect written at hour eleven is paid for during the following week by someone else.

Beck’s treatment sits next to two related ideas in the same pages: breaks during the work day, and what his index calls the fallacy of working longer to regain control. That second one is the practice’s actual target. Falling behind produces a strong instinct to add hours, the added hours degrade judgment, the degraded judgment produces rework, and the rework puts the team further behind. The practice interrupts the loop by refusing its first step.

Slack is the planning-side version of the same refusal: leave room in the schedule so that the pressure to work tired never arrives.

The Agile Manifesto states the general principle: sponsors, developers and users “should be able to maintain a constant pace indefinitely.” The word doing the work there is indefinitely. A pace you can hold for a fortnight before a crunch is not a pace, it is a sprint with a bill attached.

Signal: crunch is a rare, named, discussed exception rather than the shape of the last month.

Sources

• Kent Beck with Cynthia Andres, Extreme Programming Explained: Embrace Change, 2nd edition (Addison-Wesley, 2004): Energized Work as a primary practice in chapter 7. The book’s index routes both “Breaks, in work day” and “Control, fallacy of working longer to regain” to the same pages. Both are visible in the publisher’s free sample.
• Bill Wake, Overview of “Extreme Programming Explained, 2/e”: the second edition’s renaming of first-edition practices.
• Agile Alliance et al., Principles behind the Agile Manifesto: “Agile processes promote sustainable development.”