Scrum is pretty small. A lot of the threads on here are mentioning all sorts of Agile tools that Scrum does not require. Those extra things are optional if they help you but defined outside of Scrum (like planning poker). And if you dislike one of the few things in Scrum such as the end of sprint retrospective, you can take it out. So a lot of people think they’re doing Scrum when it’s really Scrum plus other stuff, and they think they hate Scrum. Experienced developers may not find it helps them all that much, but to me, the important other side of the coin is that when you try to teach the powers that be about Scrum, it helps educate them enough that they don’t mismanage the developers too much. To management, Scrum tries to say don’t come in and add requirements every other day during the sprint so the developers can at least have a few days of focus to actually ship some code. I’ve definitely seen overeager product owners come in and hover over developers more than is healthy for the project even AFTER being educated on how Scrum is being followed and they should pull back and give a little breathing room! If I had a nickel for every time management pulled people aside to tell them more stuff to build and then shortly after ask why something they asked for weeks ago isn’t done yet…………Scrum tries to give developers a way to communicate what needs to happen for them to ship! Maybe in some purely tech companies the folks in charge already get it and don’t get in the way so the developers can just have at it, but those are rare amidst all the types of businesses employing software developers.