>1) Burnout is not a workload problem, it is related to your subjective perception of the meaning behind that workload
When I first started in the 1990s, we didn't have scrum / sprints. We used to release quarterly (this was a software shop that sold to around 200 clients). After each quarterly release, we felt a massive sense of accomplishment, especially when hitting the deadline and our scope. We would all join up and have a party at someone's house to celebrate with a release party. We took a few days off after a release. I feel that scrum / sprint ticketing style of work really took that sense of accomplishment away, or significantly diminished it. I think this also leads to higher burnout. It feels like it's now just a ticket grind and not much of a sense of accomplishment as it was before.
When I first started in the 1990s, we didn't have scrum / sprints. We used to release quarterly (this was a software shop that sold to around 200 clients). After each quarterly release, we felt a massive sense of accomplishment, especially when hitting the deadline and our scope. We would all join up and have a party at someone's house to celebrate with a release party. We took a few days off after a release. I feel that scrum / sprint ticketing style of work really took that sense of accomplishment away, or significantly diminished it. I think this also leads to higher burnout. It feels like it's now just a ticket grind and not much of a sense of accomplishment as it was before.