Guess I’ll yell into the void too haha. Never was a huge fan of scrum, but I get why it’s there. Not every team is blessed with very senior and, frankly, trustw

Guess I’ll yell into the void too haha. Never was a huge fan of scrum, but I get why it’s there. Not every team is blessed with very senior and, frankly, trustworthy engineers. I was once one, so were you. Lacking that, you need guardrails for your developing engineers. Scrum is ONE such guardrail, a micro-management process where one is needed. The better guardrail is actually pairing up your developing engineers with helpful senior engineers indefinitely, but the less functional orgs out there don’t use senior engineers like this. The ideal team just gets work done. They communicate status and progress. They deliver. At the end of the day, the powers that be just want the results that they are paying for. They don’t care about scrum or Kanban or whatever (if they do, I’m sorry, that sounds bad— they shouldn’t). All they care about is results. It’s when results don’t happen that management freaks out, and the snake oil of scrum sounds appetizing. My $0.02.