Brian Marick’s comment in his XP Day keynote about slowing down has certainly generated a lot of interest. There were several open space discussions that touched on the topic, and now there are blog entries as well.
I was at one of the open space discussions, entitled “How do we slow down by June?” The title points to a common dilemma faced by software developers: we know we’re working at an unsustainable pace, but it seems there is always another deadline looming. I really liked J.B.’s idea of being transparent with developers about the business’s requirements. We might just be willing to work at the absolute maximum speed for a specific business goal, if we know what we’re being asked to do and why. I also like the idea of time off or extra compensation after the goal is met.