Of course, Scrum is concerned with sustainable pacing: avoiding end of waterfall "crunch", setting estimation horizons that are sustainable (developers are terrible at estimating things in two-week time periods, but developers have an impossible time estimating anything beyond that), modest attempts at preventing burn out, even regular "small increment" delivery is itself an attempt at sustainable pacing (rather than big blow out quarterly releases, for instance).
> You should reach a given point and stop.
"And stop"? I would almost pay to see a Scrum team that allows front-loading stories and pays for time off if they are completed ahead of sprint deadlines. That sounds like an incredible unicorn.
There's no stopping in Scrum. There's always "pick a new story off the backlog" and there's always an infinite backlog to pick from, in my experience.
> You should reach a given point and stop.
"And stop"? I would almost pay to see a Scrum team that allows front-loading stories and pays for time off if they are completed ahead of sprint deadlines. That sounds like an incredible unicorn.
There's no stopping in Scrum. There's always "pick a new story off the backlog" and there's always an infinite backlog to pick from, in my experience.