I used to be a diehard scrum advocate (though I've always been focused on results and not just process as magic). I've felt in my latest role, scrum doesn't cut

I used to be a diehard scrum advocate (though I've always been focused on results and not just process as magic). I've felt in my latest role, scrum doesn't cut it. Problems: - Larger team: I can't swarm developers on a single project. It's impractical for every team member to be instantly able to help out with the domain specific work. - We're a platform team and so are in the way of $FEATURE a lot. Our long term roadmap is primarily driven by other teams urgency and we have to roll with it. - Estimates are a boolean, not a date. Our estimates don't matter because unless it's a 6m+ project, it needs to be done because of $FEATURE Because of this, sprint planning is never stable long term. Every work comes with tradeoffs being made at the top level. Estimation means time away from doing work we know we're going to do unless it's a huge SWAG. I like the ownership scrum has, but the work is gonna take what the work takes. Why should we spend tons of time estimating and planning when we just need to get the work done before next product launch 6m out? Feels like Kanban might work better. I need to read up on the Basecamp model.