One very strange thing that happened to me at Skype, where we went all-in on Scrum and 2-week sprints: Sprint burnout. I got tired of the retro & planning every 2 weeks. That as soon as we finished a sprint, we'd start a new one. Got this feeling about 8 months into sprints.
Sprints sucked the joy out of what would normally be things to celebrate. We shipped a milestone, yay! Oh, but we "failed" the sprint technically. And there was never time between milestones. Always the next damn sprint on Monday. After a while, I hated it.
I always, *always* liked it more when we worked on projects. Sometimes using sprints (but only during the projects), but more often not. We focused on shipping the first milestone, the second one, the whole thing, celebrate, monitor, and - god forbid - rest after a major push.
To not only close with complaining, but constructive "what is better" points, here are two: 1. Do projects and have engineers lead them! It's what I did: https://t.co/o8ERTbq6OY 2. A deepdive in why most of Big Tech moved well beyond Scrum (or Agile):
blog.pragmaticengineer.com/how-to-lead-a-…
blog.pragmaticengineer.com/project-manage…
