> it is a lot nicer and I am honestly wondering if Scrum is even necessary when you're only with 4-5 devs.
Scrum is so woefully misunderstood.
It makes sense for small teams (yes, those 4-5 devs), if — and that's a big if — they work together on a single product. It is intended for developers to coordinate with each other, and also provides feedback loops for reality checks and for improvement of collaboration.
If those 4-5 developers work independently from one another, don't have to coordinate, don't need business to tell them what, out of various options, is the most important thing to work on right now, and don't need feedback from users to correct them along the way, then of course they don't need scrum.
Yeah, it's basically just formalized rules for communication, and I've been on teams where it worked great
I think it's awful when people follow it slavishly -- you chuck out anything that doesn't fit your team. And yeah, in the example you gave, it's a terrible fit lol
I have some stakeholders that do not know what they want and can't define it, so in desperation I dragged them thorough making fucking user stories -- user stories --and oh my god they loved it lol
They immediately started trying to apply it to everything too. I have regrets.