I know people that favor the pace of good old ‘Waterfall’ projects. It’s not that they believe that this is the right way to build software, but at least you didn’t always feel pressured. They hate the constant routine of Sprints without any respite, getting completely drained at the end of the Sprint and then the next Sprint follows immediately.
Scrum should not wear you down. Here are several pointers to avoid being trapped on a treadmill.
The Developers determine what they can take in for the next Sprint.
The Developers should determine what goes on the Sprint Backlog and -if applicable- how it needs to change to achieve the Sprint Goal.
The Developers manage their work.
The Scrum Team treats the Sprint Backlog as a forecast, not as a contract signed with blood.
The Scrum Team avoids Planning Tetris, which is the anti-pattern to fill the Sprint Backlog to utilize all the capacity. They leave room to manage complexity.
The Scrum Team uses empiricism (transparency, inspection, adaptation) to address its complex issues. Because this is why they use Scrum in the first place.
The Scrum Team seeks for ways to be more effective AND make the Sprints enjoyable.
The Scrum Team uses the Sprint Retrospective effectively. They not only reflect on how the Sprint went but also create a plan for improvements.
The Scrum Master coaches the Developers in self-management.
Do you know more ways to avoid being worn down?
And remember: the Developers determine what they put on the Sprint Backlog. They have a vital say in what the Sprint Goal is (as part of the Scrum Team) and on top of that they manage their work! The Developers have this power. Now use that power and don’t let yourself get drained.