Thread by @webmeadow

Agile & scrum friends, what’s your preferred frequency for Rest Weeks/Catch-up Sprints in a project? I like every 4 sprints; I’m interested in what you do.

If your response is “Rest weeks??”, please know that your process is damaging your team members’ health.

Rest/catch-up sprints are not about vacation and time away, but rather time to sit inside the project without the relentless pressure of pushing forward. Reorganize some user stories, clean up a hacked bit of code, adjust an internal process. Rest.

“Generous leave policies” and “we encourage time off!” only fob the burden onto individual team members. Do not pretend you are absolved of the responsibility to make systemic change in this area.

It is the nature of all things to find balance between movement and stillness. Growth and then dormancy, pursuit and then rest. Our industry, and our colleagues, are not somehow exempt from this rule.

Your project, too, is a living organism, and yearns for a moment of quiet. We all benefit from a deep breath and a considered pause. Lord knows that software and startups aren’t exactly in danger of setting aside too much time for thoughtful reflection.

“But clients won’t like it.” Clients will do what you teach them is necessary. Be brave. Or consider relinquishing your leadership to someone who is willing to do what it takes to put the wellbeing of your people first.

I'm fascinated by how many people think that agile's call for "sustainable pace" negates the need for rest. That's not how living organisms work? People go to sleep literally EVERY NIGHT. Nothing moves forward without also regularly standing still.

Also, picture me holding your shoulders and staring deep into your eyes so that you really hear when I say: Capitalism has no use for sustainability. Unless you *actively* fight against it, businesses run under capitalism will chew up their workforce without a second thought.