We talk a lot about velocity, but is work-life balance actually achievable anymore when sprints are back-to-back? I feel like upskilling in Scrum Mastery might help me protect my team better, but I’m worried that the "Agile" label is just being used to justify constant, unsustainable output.
3 answers
Agile is actually designed for "sustainable development," though many companies ignore that part of the manifesto. A good Scrum Master should be using velocity to prevent over-commitment, not to push for more. In my current role, we have a hard rule: if the sprint is at capacity, nothing else gets added without something else being removed. This approach has kept our team from burning out over the last two years. It’s about the long game. If you treat every sprint like a literal sprint, you’ll never make it through the marathon of a long-term product lifecycle.
Cynthia, that sounds ideal, but how do you deal with "Product Owners" who use the Retrospective just to demand higher story point completion for the next cycle?
I’ve found that "time-boxing" my own work within the sprint has been a lifesaver. Once the box is closed for the day, I don't check Slack until the Standup.
I agree with Angela. Time-boxing is a skill in itself! It's one of the few ways to stay sane when the backlog seems like it's never-ending.
Tyler, that’s where you have to use the data from previous sprints to show that "forced" velocity always leads to technical debt and bugs. I show them a graph: when we overwork, our quality drops, and we spend the next sprint just fixing mistakes. When I frame it as a "quality and cost" issue rather than just a "feelings" issue, Product Owners usually back off. You have to speak their language to protect your team’s time effectively and ensure the product remains stable.